Just bought and installed theme, but can't update plugin

I used this automatic feature but found that it didn’t work with me.

Start with the Newspaper Theme
Access the premium features and create your awesome website. To start, easily Install and Activate the following tagDiv plugins with a single click.

It showed like these after I clicked update and wait it for updating

tagDiv Composer
Failed
tagDiv Cloud Library
Failed
tagDiv Social Counter
Failed
tagDiv Standard Pack
Failed

An error occurred and we could not finish the process.
Please reload the page and try again, or manually update the plugins.

Hi,

Same here – Just bought the theme (again). I have this running on another site (same IP) and when updating it does the same. I’ve been using newspaper and newsmag for years (with other licences). What am I missing – I have checked the link provided above, I’m meeting all requirements (everything is also green on the system page). Site works. It wanted to update “out of the box” when I downloaded the theme from Envato, which I thought was strange…? Currently showing running 10.3.3. I will attempt to manually update.

Also – I have used a homepage style from the tagDiv cloud (Romania News Pro) that seems to be broken in Edge (who uses Edge I suppose?) – it looks all broken..

• This reply was modified 6 years by jsup.

NOTE: Be aware in my case, I just took a closer look at my deployment and i can see that I have renamed the wp-content folder to a special name (I did this a long time ago, when I thought that was a good idea haha!)

Never mind… Fixed my own issue – I renamed my wp-content back to normal and everything worked again. It looks like you have not parametised wp-content in your code checks i guess… This is the danger of changing wp-content folder names I guess.. I definitely don’t do it anymore, but I used to do it years ago (this was one of those sites that I must have done it on years ago). As for edge… I give up.

Fyi: In an effort to be part of the solution, and not the problem, just thought I would let you know that renaming the wp-content is a “supported” action, however many developers hard code the folder name making it a fairly dangerous activity – I assume this is why it broke in my situation. Maybe the team could look at following the standard whereby the foldername is actually fed by the variable..?

See https://wordpress.org/support/article/editing-wp-config-php/#moving-wp-content-folder

• This reply was modified 6 years by jsup.
• This reply was modified 6 years by jsup.