Search Results for 'update'

Update 2: Further investigations into the matter revealed that images are not loaded when I place the below code in Tagdiv Speed Booster Plugin to move scripts and styles to the footer.
soccer-engine/index.php

So, everything works fine when Speed Booster Plugin is in disabled state.

Regards
Azhar Nadeem

Update: Big Grid is working now. It collapsed because latest post did not have Featured Image attached. However, image loading issue still exists with plugin activated.

Thanks

Hi

Try to deactivate all plugins, clear all caches then activate only Visual Composer and test again. Also make sure that you also update the plugin from the same path with the theme: https://forum.tagdiv.com/newsmag-how-to-update-visual-composer-plugin/

Hope this help.
Thanks!

Good point. It’s strange.

I went back to yesterday at 11 AM (server backup) ….as I didn’t lose my Theme Panel settings until maybe 2 or 3 AM today.

Didn’t do the complete database backup though. Just going to re-do the settings.

I’m thinking it has to be the Auto Theme update.

Is 1.7.1 the newest NewsMag update?

Thanks.

I was under the impressions auto updates were off.

Do have regular backups.

Did NOT use the backup from the export in theme panel (screwed).

Good idea to turn OFF automatic updates on WordPress.

Good idea to make regular backups so you can easily restore site if something odd happens.

Good idea to backup theme settings from the export option in theme panel.

If you’re using a caching service or plugin, you might try deactivating that in case the service you’re using crashed.

Not much help at this point, I know, but all of the above are good ideas.

Obviously nobody can help you put things back how they were, but disabling automatic updates, removing unused themes and plugins, check for issues with plugins before updating (like YOAST had major bugs with new 3.0 update), etc.

TagDiv will likely have some thoughts, but the theme cannot magically kill itself in the middle of the night — only a plugin, core update, cache/service change, host crash, or hack can do that.

I can confirm that update to 2.3 and 2.3.1 was absolute nightmare. I get the same errors as @awtown. It is too risky for me to update, and I am staying with 2.2.

Yoast has now updated to v3.0.2. I have found this corrects some problems I was having (I can now select sidebars, post styles, etc. which I couldn’t before), but it still doesn’t seem to want to play properly.

Doesn’t like Visual Composer, doesn’t save titles or meta descriptions and the SEO analysis seems broken. I may need to keep on clearing the caches, but so far it doesn’t seem to be helping.

Maybe the inevitable v3.0.3 will sort it out…

Hi

That message appear because you’re using an outdated version of Social Counter. Try to delete the old version of the plugin and install the new one included in theme’s path (/plugins folder)
When you update the theme we always recommend to update the plugins included in theme’s path.

Thanks!

Somebody going to the index page in your theme folder is not normal, so that isn’t a significant error related to other issues. That isn’t a site page or anything a normal person should go to, but it sometimes gets triggered when doing updates.

Might want to
a) scan site for security issues
b) reinstall WordPress and all plugins
c) switch to default theme temporarily
d) install clean version of theme
e) retest

There’s been a number of modifications made to the child theme on our site.

So if I read your message correctly, you’re saying that to update to the new version the child theme needs to be replaced and the modifications from the previous version will likely be lost.

Fabulous!

I generally like your theme, but after this wonderful update process, we’ll probably be moving on.

Yeah… I usually wait a couple of days for new full dot versions of YOAST, as they have totally crashed my site a couple of times. They seem to push the new version out then use the customer base as the beta testers, then they do 1-4 updates, then it’s good to go.

With them moving so much to Ajax/JavaScript there is already a ton of things happening in the admin panel with JavaScript, so it’s going to cause some major funky things as it’s totally different how they’re actually doing stuff. Probably need to go through and resave every option panel in YOAST 3x to be safe (as had to be done in couple of older versions).

We’re upgrading to a ‘pro’ license with them soon, so we can report goofy stuff and get reply.

Color me paranoid!! 🙂

• This reply was modified 10 years by simchris.

The all new version of YOAST may have some bugs; hence the inevitable 3.01 dot update and likely further dot updates from Yoast. Likely good to go BACK to prior version for the moment.

New version of Yoast using various JavaScript things now in place of dbase things.

Likely major clearing of caches/CDN reset will be required.