[RÉGLÉ] Boutons Sauvegarder et Sauvegarder & Quitter non fonctionnel

[Sphyncks]

Bonjour à tous,

Voilà ma situation.

J'ai récemment migrer Joomla 1.5 à 2.5.14. Évidemment, la version 2.5 s'est installée dans le dossier /public_html/nouveau site. Jusque là, les 2 sites étaient 100% fonctionnel front-end et back-end. Une fois terminée J'ai téléchargé tout le répertoire /public_html sur mon PC (ce qui inclus les 2 version).
Par la suite, j'ai supprimé tout le répertoire /public_html et recopié l'intégralité du répertoire /public_html/nouveau_site à la racine en respectant l'arborescence.

Le site "front-end" fonctionne à merveille mais du côté administrateur, je suis incapable de sauvegarder toutes modifications aux modules, templates, articles etc...

Est-ce que j'ai fais quelque chose que je n'aurais pas dû faire. Ah oui, je dois spécifier que j'ai tenté le tout avec Chrome et IE.

Quelqu'un a une idée par hazard de ce qui ne tourne pas rond?

Merci à l'avance.

Cordialement,
JS

[Sphyncks]

Re : Boutons Sauvegarder et Sauvegarder & Quitter non fonctionnel

Bonjour à tous,

Suite à mes recherches via google, j'ai finalement trouvé la solution à mon problème. Le texte est en anglais, mais j'ai suivi leurs indications décrites plus bas et tout est revenu à la normale. J'espère que cela viendra en aide à d'autres qui ont le même problème que moi.
------------------------------------------------------------------------
Save Button Not Working After Migrating Joomla

We are migrating many Joomla websites (from version 1.5.x to the latest 2.5 version) these days and a common problem that we see is that once we finish the migration, and we make the website live, the “Save” button (as well as many button in the Joomla menu) stops working. This is normal – and it’s because our method of migrating Joomla consists of creating a sub-directory in the main website’s directory, ensuring that the website works normally under that sub-directory, and then moving the contents of that sub-directory to the directory of the main Joomla website, essentially overwriting the Joomla 1.5 version of the website with the Joomla 2.5 version. You might now think, “how are these two things related to each other?”

Well, when you migrate this way (by creating a sub-directory for the Joomla 2.5 version and then moving it up one level), you are causing some caching issues (not to mention, of course, some login issues) at the browser level. The browser becomes confused a bit, and there are two ways to unconfuse the browser and solve this problem:

Clearing your browser cache: Clearing your browser cache ensures that your browser has the latest version of your website – and that there are no cached JavaScript libraries that are conflicting with your Joomla’s functionality.
Resetting your Joomla admin template: Resetting your Joomla admin template consists of switching from one admin template to another (usually from Bluestork to Hathor) and back (when you do this, Joomla instructs the browser that its cached version of JavaScript files is not up-to-date, and it needs to be refreshed). So, for example, if you’re using Bluestork (which is the default template) as the template for your administrator area, all you need to do is to switch to the Hathor template and then switch back to Bluestork. Changing the template of your admin area can be done in the same place where you change the template for your site (under “Extensions”->”Template Manager”).

We think that this is an annoying bug in Joomla and can cause a lot of anxiety for those that migrate their Joomla websites by themselves (because they think that they did something wrong during the migration process when they really didn’t). We hope that this bug will be fixed in a later installment of the Joomla 2.5 series.


Bonne journée à tous!