joefletcher
Forum Replies Created
-
That would be awesome, thanks. When I copy over my starter site to a new install, first thing I do is clear the history log. This would help:
wp simple-history clearForum: Reviews
In reply to: [Disable Blogging in WordPress] Would be great if it were updatedThe latest deal-breaker was that it was preventing my “duplicate post (type)” functionality. Do you happen to know if that conflict was resolved?
Forum: Plugins
In reply to: [Happy Addons for Elementor] Js error – conflict with elementor (V 2.14.1)I have the same errors – when logged in, not when logged out.
Uncaught TypeError: Cannot read property ‘Document’ of undefined
at Object.<anonymous> (frontend.min.js:formatted:3601)
at n (frontend.min.js:formatted:12)
at Object.<anonymous> (frontend.min.js:formatted:3319)
at n (frontend.min.js:formatted:12)
at Object.<anonymous> (frontend.min.js:formatted:3234)
at n (frontend.min.js:formatted:12)
at frontend.min.js:formatted:72
at frontend.min.js:formatted:73
(anonymous) @ frontend.min.js:formatted:3601
n @ frontend.min.js:formatted:12
(anonymous) @ frontend.min.js:formatted:3319
n @ frontend.min.js:formatted:12
(anonymous) @ frontend.min.js:formatted:3234
n @ frontend.min.js:formatted:12
(anonymous) @ frontend.min.js:formatted:72
(anonymous) @ frontend.min.js:formatted:73
happy-addons.min.js:1 Uncaught TypeError: Cannot read property ‘handlers’ of undefined
at happy-addons.min.js:1
at dispatch (jquery.js:3)
at r.handle (jquery.js:3)
at Object.trigger (jquery.js:3)
at Object.a.event.trigger (jquery-migrate.min.js:2)
at jquery.js:3
at Function.each (jquery.js:2)
at a.fn.init.each (jquery.js:2)
at a.fn.init.trigger (jquery.js:3)
at Frontend.init (frontend.min.js:2)I have the same “issue where I delete something but it still stays visible in the elementor page builder but not in the live preview.”
Meaning, in Elementor, I can delete an element (for example, a Heading), but it will not go away. Clicking Update will indeed remove it from the live frontend page, but I need to refresh the Elementor page builder for the element to go away. And sometimes it doesn’t even go away then. (though Regenerate CSS seems to work.)
Yeah, Cloudflare has a Development Mode that turns off caching for 3 hours. It’s available through their admin or through the CF plugin.
I use nginx, so no .htaccess to modify. Still, those troubles give me pause about using this plugin.
I usually use Elementor with Development mode on so that Elementor and the frontend are not cached as I make changes. However, with the rocket launcher rules… and if this plugin cleans up the frontend cache when Elementor updates pages (and templates and settings?), then I may not need development mode.
Thoughts?
Thanks for sharing. I have Elementor editor troubles occasionally. Hadn’t thought about Rocket Launcher as a cause, but will check this out. Or, I may turn it off completely- I’m not sure it helps much but haven’t tested it thoroughly.
@maxgorky can you share the page rule you used to avoid Rocket Loader breaking Elementor Editor?
Forum: Plugins
In reply to: [Customize Pane Resizer] merged into core and disappearedThanks for discovering that. I too can’t edit css that is 320px wide. I installed this one – is the same one you installed? Customize Pane Resizer on Github
Forum: Plugins
In reply to: [CloudGuard] Gone?! Wha?Ah! got it. thanks!
Forum: Plugins
In reply to: [CloudGuard] Gone?! Wha?Thanks for your work on this. Love the plugin.
Curious though, how do you purposely store your assets on Cloudflare’s CDN? I thought they didn’t offer traditional object storage like a traditional CDN, just caching.
Forum: Plugins
In reply to: [CloudGuard] Gone?! Wha?+1 just following, hoping w.org allows an update soon.
I wrote a plugin to make Elementor the default editor, but which still gives the option to use the WordPress editor.
You can grab the code here:
https://gist.github.com/heyfletch/7c59d1c0c9c56cbad51ef80290d86df7Here’s what I think is happening. Not sure. The homepage’s amp reference is to https://www.kineticinquiry.com/?amp. All the other pages use the /amp/ version. Google’s Search Console AMP validation/error page sees the ?amp version and tries to validate it as valid AMP HTML, BUT for some reason it is validating the non-amp homepage, i.e., https://www.kineticinquiry.com/. (which is not AMP)
This is ok (/amp/):
https://validator.ampproject.org/#url=https%3A%2F%2Fwww.kineticinquiry.com%2Famp%2FThis is not ok (?amp):
https://validator.ampproject.org/#url=https%3A%2F%2Fwww.kineticinquiry.com%2F%3FampIn the meantime, I’ve done a post-HTML rewrite for her AMP reference to replace https://www.kineticinquiry.com/?amp with https://www.kineticinquiry.com/amp/ so that there is no longer any reference to the ?amp version.
So I’m wondering if the plugin should only ever use /amp/ and not ?amp ?
Hi @ampforwp,
I’m helping @wanttogetwptowork with this. We updated the plugin to Version 0.9.35. On the homepage, the rel=”amphtml” points to href=”https://www.kineticinquiry.com/?amp”, which does work. But /amp/ works too, and /amp/ is what is used for the rel=”amphtml” on other pages.
So, we’re confused why it’s different on the homepage. It may not matter, but Search Console was complaining “Google systems have detected that some of your AMP pages (https://www.kineticinquiry.com/?amp) do not meet our guidelines and will therefore not show in Google Search AMP-related features. User-authored JavaScript found on page”. This is the only AMP error Search Console reports.