Log In
Register
Home
Add Reply
Add Topic
Topic RSS
QuoteAre you seeing any javascript errors when you try this and it fails? That is the most likely cause. Can I suggest that first you try it on a different browser (different js engine). It should be pretty quick so if nothing happens after, say, 20 seconds, try it again. The few people who see this problem report success in the end.
We have made changes to the methodology used for upgrading in 4.2 even though we have never been able to figure out the problem a few people have.
Yellow Swordfish
No luck using another browser. I'm operating on a Mac with OSX10.6.2. Tried Safari and Firefox. Next I used Explorer under XP. Still no luck. How do I revert back to the previous version so I can at least get back up?
You will need to restore from backup to revert to old version.
Still don't know why such a small minority (couple of handfuls out of tens of thousands) have this issue. Drives us crazy. We have made some changes in the installer in 4.2 hoping to put this to bed.
Were you ever able to check the error logs (sorry if you answered prev – on my phone)
Visit 12:16 pm
SP Master
Nov 9, 2008
Offline
Steve - wont need to go to backup as (1) he upgrade didn't run and (2) assuming he was on 1.4.2 prior to ths then the upgrade script actually does nothing but bump up the version number.
So – as long as this IS from 1.42 t o1,4,3 then in theory he could chage the version number directly in the database and it should be fine. What do you think
Yellow Swordfish
Ran into another issue with old V4.1.3. While review options to the setup, I am now getting "ahah error: 404 OK". What is this? This is happening after I restored the Forum after aborting the update.
404 means a file could not be served to the browser. There are most commonly two reasons. The file is physically not there or the permissions on the file (or it's folder) are incorrectly set.
All the forum 'admin' files are in the /admin folder and only you can determine if they are all there or not. As to permissions, SPF folders should be set to 755 and files to 644. This is especially the case for all files in 'ahah' folders. Many hosts will deny access to them if, for example, the permissions are too open (such as 777).
Worth noting that it can also be a by-product of smething in your .htaccess file which might also be worth updating (from your blog permalinks panel)
Yellow Swordfish
Thanks for the reply. I could not find any missing files by comparing the files on the updated security release with what I have on the server (previous version). Permissions appear all in place as advised. I updated the .htaccess file via the permalinks panel but no change. This is what I have in the .htaccess file. Do you see anything amiss here?
no, that .htaccess looks fine…
and what does 'old' 4.1.3 mean? did you upgrade to 4.1.3? if so, did you properly name the folder simple-forum and remove the old version? the name must be exact and you cant have two versions in the plugins folder…
would also help to take a look at your server error logs too and see if there is any more info in there…
Most Users Ever Online: 444
Currently Online: Conrad_Farlow, steve.engelking, jawaulk, irlandes1, joelrob
77 Guest(s)
Currently Browsing this Page:
2 Guest(s)
Top Posters:
-Radio-: 1251
Lee H: 606
Luffer: 535
Conrad_Farlow: 502
jim: 478
neon: 263
ovizii: 240
Tal: 240
Member Stats:
Guest Posters: 2626
Members: 7363
Moderators: 1
Admins: 2
Forum Stats:
Groups: 5
Forums: 16
Topics: 10897
Posts: 79582
Newest Members: Rick Thomas, joelrob, ndc, MacBravO, irlandes1, triphop, betokan, Jonathan Yovani Muñoz, somosguatemala, ahcreate
Moderators: Brandon C (162)
Administrators: Yellow Swordfish (22240), Mr Papa (23688)
Privacy Policy
