Notifications
Clear all

wpForo 1.x.x [Closed] Problem upgrading from wpForo 1.3.1 to 1.4.2

10 Posts
3 Users
0 Reactions
2,667 Views
Posts: 22
 GJC1
Topic starter
(@gjc1)
Eminent Member
Joined: 7 years ago

I have a hosted Wordpress site with wpForo 1.3.1.

I tried to upgrade to 1.4.2 using the "update now" option and it failed with the error as shown in the attached file.

After trying the update the entire website was unavailable.

We got the site up and running again by renaming the wpForo folder - and then got the 1.3 version working again by reactivating it.

I am also using wpForo Advanced Attachments 1.0.3

Any thoughts on what went wrong and how to effect the upgrade without any problem?

Thanks, Graham

 

9 Replies
Posts: 1602
(@anonymous20)
Noble Member
Joined: 8 years ago

Is that a by any chance a Windows server ?

In any case enabling WP Debug to a LOG will tell you (probably) the real error.

 

 

Posts: 22
 GJC1
Topic starter
(@gjc1)
Eminent Member
Joined: 7 years ago
Posted by: Anonymous20

Is that a by any chance a Windows server ?

 

 

It's a hosted Linux server

There's nothing obvious I can see in the log file - but I don't want to try again with debugging on (if I can work out how to do that!) as it would probably result in the site going down again.

Thanks

Posts: 1602
(@anonymous20)
Noble Member
Joined: 8 years ago

You mean you have ENABLED Wordpress Debug to a log, trying to update wpForo and nothing is logged ?

Are you 100% sure ?

https://codex.wordpress.org/Debugging_in_WordPress

Posts: 22
 GJC1
Topic starter
(@gjc1)
Eminent Member
Joined: 7 years ago
Posted by: Anonymous20

You mean you have ENABLED Wordpress Debug to a log, trying to update wpForo and nothing is logged ?

Are you 100% sure ?

No - sorry.

There is a logfile produced by default and there is nothing in there.

I haven't explicitly enabled Wordpress Debug (thanks for the link)

However, I don't really want to try the upgrade again - even with debug enabled - as I expect it would take the website down again. So trying to determine whether this is an issue that has happened before - but appreciate I'm not able to provide much useful information.

Page 1 / 2