I upgraded from 1.5 (1.6 was a disaster) to 1.7 and the original problem with the blocks page disappearing resolved itself, but now accessing /blocks or /themes, the only two I tried, took waaay to long, like a minute.
Something's broken.
I upgraded from 1.5 (1.6 was a disaster) to 1.7 and the original problem with the blocks page disappearing resolved itself, but now accessing /blocks or /themes, the only two I tried, took waaay to long, like a minute.
Something's broken.
Comments
Comment #1
ibex commentedI upgraded from 1.5 to 1.7. (Directly after the installation of 1.6, I discovered 1.7 and installed it.)
However with version 1.7 I cannot access my /admin/* pages anymore. After some time (timeout?) I get a page not found message on the requested page. A DB log entry for such a page:
I've reverted to version 1.5 and /admin/* are accessible again, i.e. the problem disappeared.
This problem could be related to the above report.
Comment #2
jose reyero commentedThis may be related to #905428: Multiple issues with i18n variables: wrong multilingual variables, cache rebuild, etc..
Please give a try to -dev version and use the Variables clean up page.
Comment #3
LarsKramer commentedHi, I just upgraded from 1.6 to 1.7, and I am no longer able to change site status from offline to online. I suppose it's related to this issue... Once I disable i18n, the problem goes away. I tried clearing all caches.
One note: I recently changed the site's default language. I know it's not recommmend, but I had to, and until now it hasn't caused any major problems.
I went back to 1.5 as it seems to be the most stable version atm. Thanks for all your work :-)
Comment #4
logicing commentedSame here, every single admin page takes forever to load with version 1.7. I also tried the -dev version as suggested, to no avail.
Rolling back to 1.6 until this is fixed...
Comment #5
ibex commentedThe speed of admin pages was normal again with i18n 1.7 after cleaning the table i18n_variable. I've directly cleaned the table i18n_variable with SQL.
Thus, I'm marking this issue as duplicate of #905428: Multiple issues with i18n variables: wrong multilingual variables, cache rebuild, etc...