Search Results for 'update'

Flash is not supported by most web browsers by default anymore, being an end of life product (https://blogs.adobe.com/conversations/2017/07/adobe-flash-update.html) and blocked by most modern ones, so should generally no longer be used — or start winding down if you have no choice “right now.”

What browser are you using, do you have Flash installed in browser, does your browser support Flash?

Theme has zero control over Flash content.

If you paste it into a post using the text editor, and it doesn’t work, it means something is wrong with what you’re entering, or your browser doesn’t suppport Flash playback.

( I don’t work here. Just feedback on the obvious possible issue. ) 🙂

a) check your system status
b) you can’t edit a page built with ‘VC’ with ‘TDcomposer’ – you need to make new one
c) clear all caching
d) check for problems with plugins, like Yoast SEO has had bugs — two updates this month(!); try disabling plugins to see which might be causing issue
e) WordPress security update this week; always good to clear transients with WP-Optimize after update AND resave permalinks to clear all micro-caching
f) is using any ‘auto optimization’ plugins, these can break things — disable, or selectively disable minification options

Also note if something “suddenly stops working” it’s because “something” changed on your website. You need to stay on top of what you’re doing — e.g., if you have auto-updates for WP turned on, what got updated? Why? What changed? Did you keep copies of earlier version to roll back if plugin update actually has bug in it trying to fix prior bugs? (ahem, Yoast!).

Food for thought anyway.

Simion and Bogdan, you guys are fantastic. That last little bit has done the trick. It needs just a wee bit of tweaking but I think I can manage that myself, as you guys got the hard bits done. Thank you for putting up with my constant questioning. I’ll probably extend the service to 12 months rather than the default 6, as I’m impressed how much help we get, even though that’s a bit beyond what is meant to be done.

I’d suggest this sort of style as an additional post template in future updates. I’ve seen this style on a lot of sites and it does tend to look very impressive and modern.

Thanks for the help guys, much appreciated.

Hi Simion,

Thank you for the reply. I guess the Mozilla I have on system might need a quick update check. If possible can you mention the Mozilla version you ran to give me some bearings.

In terms of the subscription option I am planning to check the ‘Newsletter Plugin’. Will try and post my results. Although my request to you would be add it as a part of the stock theme in your next update but that is completely your team’s call.

Thank You

Chris,

The auto wordpress update was fire and at another website with Newspaper but all is ok. All plugins was at the latest version.

Take a look: http://soccerplus.gr/

All works perfect

What can I do?
Why my website was broken?

It is related to the fact that the site is served under https?

Thank You!
Sotiris

Auto update generally not great idea; but did you try since you should be doing a site backup PRIOR to any WP update (just as it says in the WP admin panel) — but try:
a) clear transients with wp-optimize
b) clear all caching
c) resave permalinks ?

Welcome to WordPress!

( I do a and c every time I update anything! )

Not really a theme issue; it’s an inherent issue with WordPress.

If you read up on this, you may find the plugin “maintenance mode” helpful, as this is the kind of thing that is good for.

Neither Theme (any theme) nor TagDiv are responsible for how WordPress ‘behaves’ when you change themes, or do any update to WP, themes, or plugins — that error comes from the fact your site is still being pinged, and sitemap in place, and suddenly the theme is not there, then it is again.

So — a permanent solution is to either ignore the issue as it should only happen once in awhile and Google doesn’t care, nor is it a “server issue” — it’s basically the fact that public should not be going to that folder.

So
a) either create a solution with htaccess like I did, or
b) learn to use something like the ‘maintenance mode’ plugin
c) mark fixed, ignore – move on with your life, per my prior posts 🙂

Food for thought anyway.

Not really a theme issue, so any help/advice you get on this forum will be voluntary, and not mandatory from staff or users.

• This reply was modified 8 years by simchris.

I don’t think that a generic article is going to help me fix this error.

Please read the related tickets that I linked to in my original request (above):
“Chris S #192272
Sep 7, 2017 at 1:44 am
This happens when you update theme or main WordPress …

nothing to fix; normally you will have one of these, unless hacker slamming that directory. So, with one you just mark as ‘fixed’ and move on.

That should so be in the WP documentation — which they are finally going to redo (won’t be called ‘codex’ any more for 2018!). ?”

“Chris S #192418
Sep 7, 2017 at 7:09 pm
I think we did something on one site for that,
we made an index.php file that had a refresh header …

although I think we then instead did an htaccess file for the them folder,
and did 301 redirect for index.php to home page of site. Something like that.

Downside is you need to replace those each time theme is updated.

Or, just grimace when you do theme update and month later see that single entry in your search console. I usually just go “(sigh) … stupid Google…”

I mean, how stupid do you have to be in the data mining business to not auto-ignore /wp-content/themes/ for indexing ANYTHING? Duh.”

I have found a possible solution on other support forums:

Hi!

Yes, having read the Yoast article https://yoast.com/dont-block-your-css-and-js-files/ i’d suggest not blocking all theme resources, however i think index.php should not be read directly by crawlers (or visitors) because it will always result on a PHP error, you could try one of these two workarounds:

Redirect theme index.php to root (this will apply to all visitors), .htaccess code (you could extend this to child theme directories or plugins):

RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /wp-content/themes/enfold/index\.php\ HTTP/
RewriteRule ^wp-content/themes/enfold/index\.php$ http://DOMAIN.com/ [R=301,L]
Or simply disallow only index.php in the theme folder, robots.txt code:

User-agent: *
Disallow: /wp-content/themes/enfold/index.php

Please advise.

• This reply was modified 8 years by miket.

Okay, one last update: The mobile version of the FBC home page is still pulling up the weird menus, even though desktop PC browsers seem to be accessing a proper version of the page.

Thanks again for all of your time and help with these things!

Thank you, Catalin.

The site does indeed seem to be working now. Not sure what caused the favorable turn, to be honest. It just began looking and operating properly after I had stepped away from it for a few hours.

I am, however, now having the same problem at my other site (www.FireBreathingChristian.com) where I just went through the same process. Additionally, I am having trouble getting my theme activation to process properly.

The main problem is the look of the site, though, with the same weird menu items showing up at the top of the page.

Here are a few screenshots (starting from the top of the home page as it looks now after the theme update):

And here’s how the same home page looked before the update:

Any help or insight you can offer will be much appreciated. Thank you for your time and assistance!

There was bug in Yoast. If you updated to new version and cleared all your caching, that might have fixed it.

Update: I activated the deactivated and activated Yoast Seo and it is working fine now. Strange

In the next update, you can not insert the schema.org/article on the control panel as it is now using the JSON-LD format.