Error when updating from 1.5 -> 1.6

I have tried 5 times now.

– Stop my nginx server
– Delete the newsmag theme folder
– Upload new newsmag theme folder
– Chown on all files to www-data
– restart nginx server

The server is returning blank page, and no access to the wp-admin folder.

Then restore 1.5 newsmag theme folder, and we’re back up.

Any ideas.

Same problem trying to clear all cashes, delete old theme, but no result, white page

It’s broken for me too with Child-Theme btw,

I wonder if it needs updating or what went wrong..

• This reply was modified 11 years by DavisBeatz.

Suggestion: You can follow my “move to newsmag from newspaper” sticky, as it’s really the same process for upgrade.

Saying that, I have not yet done the upgrade, but will be doing so later today from 1.3 on one site and from 1.4 on another.

Crashed my site as well.

After the crash I renamed the “CRASHED” Folder and upload the whole new theme folder via FTP. It failed as well. I then uploaded the 1.5 theme folder I had via FTP and I was back in business.

Well.

Deleting the theme folder, and replacing with the new one. What could be done wrong, as long as permissions are set, and caches are cleared 🙂

I updated as per usual via FTP and it did the same error. CRASH the site gives a completely blank white screen, can’t access front or backend. This the first update that ever did that since using NewsMag. I downgraded my theme back to 1.5 and it completely fixed the issue (and I am also using child theme by the way so I normally just update the main theme with no issues), so something is up with 1.6 somewhere in the codes.

• This reply was modified 11 years by shae101s.

I guess some people are not having issue, some are….

you can “try” this as one last resort; or wait for tonight / morning for official support reply on this issue.

You can TRY this method — which is what I do; might not apply to your setup:
https://forum.tagdiv.com/topic/how-to-guide-to-moving-from-newspaper-to-newsmag/

They have since acknowledged that something is wrong:

Radu replied to my comment on the Themeforest page stating:

“hi,

we have an issue with the older social counter plugin. The fix is in the themeforest queue and I will get back to you when it’s online.

I’m very sorry about this, Radu O.”

So maybe that’s what’s causing the issues. Anyone who’s using the plugin is going to see some errors/face problems till they fix it. Maybe if we deactivate that plugin that can fix for now?

AH!!!!!!!!!!!

good update, @shae101s

thanks!!! 🙂

Edited to add: they do recommend deleting that plugin as they mention to do this on another commenters post over on Themeforest:

Fix:
please delete the social counter plugin via ftp. It is located in : wp-content/plugins/td-social-counter
upload the new version that is found in the zip that you downloaded from themeforest
if you don’t manage to fix it, please send an email with your FTP details to contact@tagdiv.com with the subject ASAP FIX

Same here, 500 error.

I followed the steps of topic suggested by Chris and the update is working perfectly now.

Thanks!

Supposedly there is a bug in the TD social counter widget (update pending!!), which is why some folks getting error, some not. This is why my upgrade guide, suggests updating and then testing site with just visual composer on and nothing else then going from there.

——–

@shae101s
POSTED:
Feb 26, 2015 at 7:30 pm

Edited to add: they do recommend deleting that plugin as they mention to do this on another commenters post over on Themeforest:

Fix:
please delete the social counter plugin via ftp. It is located in : wp-content/plugins/td-social-counter
upload the new version that is found in the zip that you downloaded from themeforest

if you don’t manage to fix it, please send an email with your FTP details to contact@tagdiv.com with the subject ASAP FIX

I deleted the plugin and now 1.6 works.

Yep! Alls well now..I simply deleted that older plugin..upgraded to 1.6 then installed the newer version of the social counter included in the new 1.6 folder and everything is running smoothly again with 1.6 yay! Hope that helps others who were facing the issue.

hey guys, hows it with js composer ? which version we should use? the one which comes with this update or the one which came with version 1.4 coz the one which came with version 1.5 did not work
thx

Use the version that comes with 1.6 if using 1.6

hey guys just to give you an update on my update from 1.5 – 1.6 .. it wasnt pain as much. Currently on version 1.6 runnig as charm.. however i had to do couple of thinks to make it work.. the best way to do it is to delete all files from ftp related to theme and copy all the new files.. i had a issue with the composer again.. as it uses to much resources ..and the web was prety slow .. i am on version which came with 1.4 update of the theme.
i dont need those fancy things which are in the new version of js_composer..:)

I hope that tagdiv updates their update info on this version 🙂

/Jens

I also use Nginx, but fortunately I have not done an update theme yet. I will hold until everything is okay, but some above tips are very useful. Thanks brooooooo 😀

I was able to upgrade from 1.4 to 1.6, and also am using the older version of the counter (3.2), and all seems to be working. 🙂