On login error: "Checking for updates"...2 users found helpful
Does anyone have any experience with the following issue:
when i log in with a NOT superuser account i get a loading popup with the message "checking for updates". I can't get out of this...
The error occurs here with Concrete5 v5.5.0 in safari firefox and chrome.
Thanks in advance.
firebug gives me a "jQuery.fn.dialog is undefined" inhttp://x.x.x.x/xxxxxx/concrete/js/ccm.app.js?v=......
Has anyone had any luck with this before I start the massive task of rebuilding the site?
I'm guessing something changed in 5.5.0 since that is a step I missed out (although I wasn't offered it in the auto-upgrade). However. My gut feeling is that it probably wouldn't have made a difference.
I'm in no way advocating anyone should do what I'm about to tell you. I'm just recounting my experience and I'm quite confident doing this sort of stuff.
Anyhoo. Same error as you. Well, two errors in the ccm.app.js and I also had two files not found, "quicksilver.js" and ccm.layout.js. Put the two files in from the previous install in and ended up with just the two errors.
So there I was. No edit bar (yes the loader:helper(footer.php) was in there) and up pops the "checking" and then I'm left with the modal overlay so cannot do didly squat. So trying to be trixie, I type in a known dashboard url. Whoops, 500 server error. Spent the next 2 hrs trying to figure our whats going on (it was fine on the Xamp install). I don't really get very far, because I cannot go into the dashboard and change stuff.
That's the point I gave up on 5.5 and decided to go back to 126.96.36.199 and let my users get back to the goodies. I took out the upgrade define in the site.php and now my website looks a bit odd, but seems to be working-obviously need to clear the cache!. Log in to the dashboard. Hmmm, now there is no site-wide settings (where the "clear cache" would be) and I have other buttons like Dashboard, Dashboard Display et al.
So really peeved by now and decide enough is enough. I fired up phpMyAdmin and imported the DB backup that I'd saved. Then I fired up Filezilla and deleted everything in the cache directory. That done, still have no site-wide settings and these useless buttons that take me to blank pages where useful buttons used to be (bugger).
Since I had also done an entire site backup from within Cpanel I was happy to delete all the tables in the database, use phpMyAdmin to restore the db from the cpanel backup and smartly followed that by the backup from concrete5 (they were different) and finally (4 hrs later) I'm back to 188.8.131.52. Two mins to upgrade. 4 hrs to downgrade.
I really should listen to my own advice. "If it aint broke, don't fix it".
Now i created another user (i already tried with 3 others) and all of the sudden the problem was gone for all the users...
So the problem is gone here but it still bothers me i don't know what caused the issue...
When anybody finds out please let me know!
Happy bunny now :)
I managed to find a sql backup from a few months back.
So, did the long winded method of re-building the database tables and going back to 5421. Then did the 5422, 550, 551 upgrades in order.
Now it works fine!
I also have plenty of sql backups too!
Cheers for the help guys!
After fixing the spinny checking for updates nonsense last night. I did loads of work on my site. Nothing major, just shifting blocks around and adding content.
I've gone to log on just a few moments ago and guess what's back?
Stupid spinny thing!!!!!!!!!!
On a fresh install the spinning update wheel appears also, but it disappears again after showing some information, or in other words: it behaves normally. So, I guess it has something to do with old entries in an existing database.
INSERT INTO Config (cfKey,timestamp,cfValue,uID,pkgID) VALUES ('NEWSFLOW_LAST_VIEWED','2012-01-27 00:47:23','1327621643',1,0)
and the same for the users with ID 2 etc. I only hope this helps permanently.
Fixed. I'm guessing from the information in the config and user tables that this issue will probably resurface all too frequently.
But at least this gives me a quick fix.
Thank you :)
We’ll see if it works all right permanently or if it will cause new errors.
Any official word on this bug?
FYI: There are a few questions like this, listing here to save some finding.
It points to the answer in, but yet to get it to work:
interesting to see if this works for others.
i would like to know if this is the official fix.
Works fine and the super user can get updates like before.
<?php $u = new User(); if($u->uID > 1) $u->saveConfig('NEWSFLOW_LAST_VIEWED', time() + (24 * 60 * 60)); ?>
This is crazy... LOL
Can someone post a step-by-step resolution?