Corey Worrell

@ihomefinder I think you misunderstood. This is not theme specific, it is a built-in WordPress feature called full site editing.

Oh I see what you mean. That could be valuable, but there are other config options that Google allows you to set as well. So I could see it being unwieldy to add a field for each. For now I can just disable the tracking code and add it manually via Tag Manager or custom snippet plugin. Thank you!

I understand. Do you mean you would add a database option but not provide a UI for it? That would effectively be the same as it is now, since there is filter to hook into, I could add my own UI (ACF for example) to save the value and then feed it into that filter hook.

@ndiego, any thoughts on this yet? Thank you.

@caseproof thanks very much for quick response!

I’m sorry, but this is not a plugin conflict. It’s directly caused by the code in this plugin file I mentioned above. It happens for sure on iPhone, and in Firefox. If you have a long timeline, scroll halfway down, resize the viewport, and you’ll see it scrolls back up near the top of the timeline. This happens often on the iPhone since the viewport changes as the address bar is shown/hidden while you scroll.

@auctollo thank you for the quick response!

@niklasinpsyde that is a disgraceful stance to take and a very bad developer practice. You released a broken version and then a fix with the same version number. That is not something to take lightly no matter if it is within the WordPress repository or a third-party service.

Same problem here as well. Not sure why they would choose to release a fix with the same version as a previous bad release.

Fixed screenshot https://pasteboard.co/iKx6CYQ4DZSl.png

@saifislam01 Thank you. You say “by default”, so is there a way to modify this default behavior to accomplish it?

Also getting this message, just when viewing homepage.

Notice: Undefined index: dirname in …/wp-content/plugins/resmushit-image-optimizer/resmushit.php on line 112

Another possible solution

RewriteCond %{REQUEST_URI} ^/wp-content/cache/cache-enabler/ [NC]
RewriteCond %{ENV:REDIRECT_STATUS} ^$
RewriteRule ^ - [F]

or 404

RewriteCond %{REQUEST_URI} ^/wp-content/cache/cache-enabler/ [NC]
RewriteCond %{ENV:REDIRECT_STATUS} ^$
RewriteRule ^ - [R=404]

@coreyk I used the exact snippet you pasted above.

@coreyk that causes a 500 server error. I don’t think it’s possible to set variables like that either. As far as I know rewrites can only reference capture groups, not other variables.