Moodle 4.0 problems with Moove 3.11.05 theme (the site is not showing breadcrumbs) - moodle

Basically I've installed the Moove 3.11.05 theme and everything seems to work except the breadcrumbs. I've done the research and didn't find any solution. Has someone else encountered this problem and how can it be fixed?

Moove for Moodle 4.0 is already available. You can donwnload it from its page: https://moodle.org/plugins/theme_moove/versions

There are significant changes to the user interface in Moodle 4.0 - many of which will require changes to any custom / third-party theme.
If you want to use any such themes with Moodle 4.0, then the best advice would be to hold off upgrading until the maintainer of that theme has released a Moodle 4.0 version.
In the meantime, you may find some useful information at: https://docs.moodle.org/dev/Moodle_4.0_developer_update

Related

How to migrate from TinyMCE 4 to TinyMCE 5 - Prestashop

A day ago my prestashop website, in the comment box of the blog started to display the following message:
And entering the post that explains how to migrate the version of TinyMCE , I do not understand very well how to perform these steps in my prestashop.
How can I update this?a
if you are using a third-party module to make your blog it might be is including its own version of TinyMCE. You should try to dig in its code to understand that.
If this is not the case, the blog uses TinyMCE which is normally included in Prestashop core.
On said that, this second case is likely to be the one. Update the e-commerce unlikely will solve your problem. I honestly don't remember in which version they are with TinyMCE but doing an upgrade like that might break back-office editor forms so I don't think they are keen on that at the moment. They are doing a major rollover to Symfony, I am pretty sure this is their priority right now. As said in one comment, Prestashop's dev team has to solve the issue on their side.

Contao 4.4 custom elements

I recently switched from Contao 3.X to Contao 4.4. So far so good. I like it very much. Especially working with composer.
Currently, I am looking for a solution, to create custom content elements. In Contao 3.X I could do this with the extension dma_elementgenerator (https://github.com/DMAGmbH/dma_elementgenerator). Now it looks like it's deprecated and not usable in any Contao 4.X version.
Has anyone a solution (or at least an idea) how to create custom content elements?
Example: I have to display a section with some progress bars:
I'm just looking for a way to manage those stats from the backend. Actually, I just need following custom fields:
Title
Percent
Colour
I was looking for a possibility in the last few days, but I couldn't find any. If there is no direct solution: has anyone a tip/howto, so I can possibly create a new Contao 4 extension by myself?
Never created an extension in Contao 4.
Currently you can use rocksolid custom-elements[1] by Martin Auswoeger.
He has already ported them to Contao 4.
Other extensions will follow soon.
If you really want to create your own extension, there is plenty of information available in German from various talks on the conference website, the website of the Contao Nordtag and so on.
Sadly almost none in English so far but we will change that.
For beginners, I always suggest to grab a small contao extension (nowadays called "contao-bundle") from github or packagist and read the code.
[1] https://github.com/madeyourday/contao-rocksolid-custom-elements
Received a solution from another forum. There is a way to install Contao 3.X extensions in Contao 4.X.
The how to is in german, but maybe someone will need it too:
https://www.marcosimbuerger.ch/contao-kurzanleitungen-details/contao-3-erweiterung-in-contao-4-installieren.html

My Joomla Backend is destoyed - only Text no graphics

my Joomla-backend ist destroyed. i can do a log in in a normal way, but then i see only text, no graphics. and also the wohle site is not visible and i can't scoll it. i made a screenshot, please look at it to see what i mean. i have to upgrade my Joomla Version but i cant do it with this broken backend. The current Joomla Version is 1.5.26
So, how can i fix this? I need full acces to my backend. Please help.
This is why we should not use older version of joomla.
you must install newer version of joomla
It is more reliable and secure.
Here is the step by step migration process

Why can't I find the default Magento theme being loaded?

Should be pretty simple. I am trying to find what theme is being loaded in Magento to create my own custom theme. The problem is the mine (ver. 1.7.0.2) has no files in the frontend->default->default folder so I can't put any print statements there or see which template Magento is loading to learn more about it. Print statements in base->default don't seem to work either.
And where is the home page template located?
I don't know why Magento makes this so hard or maybe I'm just looking at old info that's not applicable anymore.
Turn on template path hints. Also disable the cache from System > Cache Management while you are doing any theme work.
+1 for other answer suggesting you turn on template path hints. That is a great way to figure out the structure of how things work in Magento.
I would also recommend the user guide. It's been updated to apply to 1.7. You used to have to pay for the guide but they make it available for free now.
http://www.magentocommerce.com/resources/magento-user-guide
As well as the latest designers guide that has info specific for templates etc.
http://www.magentocommerce.com/design_guide

TinyMCE upgrade an modified editor to the latest version mayhem

It is this sad moment to a developer's life that he has to maintain and fix legacy code... In my case I have to deal with a modified (core scripts) tinyMCE 3.2.2 which I have to update to the latest version in order to play in IE9+...
So my question is if there is a way to check which files have been changed since version 3.2.2 and try to update only those cause it is an overkill to check all the code for the modifications...
Thanks in advance
I fear there are so many changes in so many files that most of them have changed since then and in order to work with IE9.
If possible you should never ever modify the core code. Instead use custom plugins if possible.