slomeli79

Not seeing it. Where exactly in /wp-content does the plugin save originals of images that it has optimized?

Bumping this with the same need. Other contributors of the site need access to create SEO friendly links, but do not need full Admin user account privileges.

Where does wp-image-optimization save/backup the originals?

Same question here. I changed my media size settings and a regenerate-thumbnails didn’t touch the already-optimized images.

How do I reset/restore originals so I can re-run the optimization process?

Found the problem on mine – Autoptimize plugin with HTML minification enabled. Soon as that was disabled, both GA dashboard and MI tracking was back.

Ref: https://www.ads-software.com/support/topic/plugin-stopped-google-analytics-tracking/#post-9422561

• This reply was modified 7 years, 7 months ago by slomeli79.

Frank,

After some extensive troubleshooting, I just discovered the same.

Have WP Rocket and Autoptimize (AO) on a site where they’ve coexisted and optimized peacefully. I moved the HTML minification job from Rocket to AO last week and apparently all GA tracking stopped. Soon as I disable HTML minify in AO, GA tracking resumes.

Re-enabled HTML minify in Rocket, and all is good.

Same experience here as of the 11th when updated from 6.2.1 to 6.2.2. Rolling back now to see if reporting resumes.

That makes sense, Thanks Derrick. That might be helpful in the Installation text – that JS settings in WPR are carried out by this plugin once it’s dropped in. (In other words, this does nothing if you don’t “tell” WPR to optimize JS.)

Works like a charm. Can optimize JS properly even when WPR’s own optimization breaks sites.

This is the holy grail all us GPP and Elementor users have been waiting for.

So far, StylePress and Anywhere Elementor Pro have developed plugins that sort-of address this.

Erfan,

I created a draft post with the default WP editor, and I create my EasyAzon shortcodes there, and then copy/paste them into the text widget in the Elementor interface.

It’s not exactly Elementor’s issue, just a limitation of some plugins, but it still does what you need using this workaround.

+1 Same thing. Rolling back to 1.4.2 seems to fix the problem for now.

Good to know it isn’t just me! I’ve been troubleshooting 20+ plugins all day to track this back to AIO WPSec, restored a backup to known-good and verified again.

Steps to replicate the issue:

1. Go to my custom login URL (ie /heyloginhere/ ), try to log in.

2. Response back is blank except for “Not available.”

3. If I delete the login URL path and go to just the base domain (ie https://www.mysite.com), the site pulls up and I see the Admin Bar. However, clicking on anything in the Admin Bar just returns the “Not available.” error.

4. SO, I logged into FTP and renamed the “all-in-one-wp-security-and-firewall” folder to something else.

5. Logged out and back in (using /wp-login.php, because the custom login URL no longer works with AIO disabled). I still get an error indicating login was unsuccessful, but when I go to the main domain now, the Admin Bar links actually take me to their expected endpoints.

6. I can browse around the site and Admin area without issue, until I log out attempt to log back in. Then I’m back to Step 2 above.

This just started yesterday, I believe just after updating to the most recent version. Can’t find a downloadable of it or I’d just roll back and wait until the next one’s out or this one’s stable.

( Confirming I disabled P Rocket caching plugin, the Limit Login Attempts plugin, etc. to verify all the above. This issue is definitely the AIO WPSec plugin and happens even without caching. )

• This reply was modified 8 years, 3 months ago by slomeli79.
• This reply was modified 8 years, 3 months ago by slomeli79.

THANK YOU. Was going nuts trying to figure out why my changes in Grid Builder would not save. Found this, deactivated Yoast while making changes, and – it worked.

Same question.

Lots of us being affected by this latest update. Seems that rolling back to older versions resolves it. (I just installed v 1.22 from the Developers tab and everything’s working again.)