born2excite
Forum Replies Created
-
Hello Simeon Boev (@k3llanved)
I’m not sure you understand the problem. The Speed Optimizer plugin itself generated 9,440 files adding up to more than 10 GB in size. For example:
siteground-optimizer-combined-css-00481e2423f4fac0b11e6f2e6157cc61.css
I have 9,440 such files in the Siteground Optimizer Assets folder. The Siteground plugin has created a new combined assets file 9,440 times and has not deleted the old files. The Siteground plugin is best suited to clean up after itself.
You’re telling me to look at each of the 9,440 files to determine which plugin created the dynamic content! The Siteground plugin created the 9,440 files and It’s not cleaning up after itself, that’s what’s important.
If I hear you correctly, deleting these 9,440 files is safe and I should then clear the cache, is that right?
Cheers,
JulianHi Animesh Gaurav (a11n) (@bizanimesh)
Thanks for your detailed reply. I appreciate your time to investigate and explain your findings.
Sorry for taking so long to get back to you. Please close this support ticket now.
Cheers,
JulianForum: Plugins
In reply to: [WooCommerce PayPal Payments] JavaScript file – muse.jsHi Inpsyde (?@niklasinpsyde?)
Thanks for your help. That’s all for now, please close this support ticket.
Kind regards,
JulianForum: Plugins
In reply to: [WooCommerce PayPal Payments] JavaScript file – muse.jsHi Inpsyde ( @niklasinpsyde )
Thanks for your quick reply and careful explanation.
If I understand properly, the JavaScript file I’m concerned about, muse.js, is legitimate because it is being loaded by the PayPal SDK. Is that right?
If you are confirming this JavaScript file is legitimate, I don’t need to take it any further.
BIG thanks, Inpsyde.
Cheers,
JulianHey?Nithin – WPMU DEV Support?(@wpmudevsupport11)
Sorry for taking so long!
I run the conflict test on a staging site because deactivating all plugins cause too many problems and too much of a hassle afterwards. I can destroy the staging site after the test then start again easily.
Unfortunately, as I explained earlier in this support case, the live and staging sites behave very differently and I’ve never been able to figure out why.
With Conflict Test
Waterfall results https://gtmetrix.com/reports/staging2.oohlalazouk.com/yDmdOfED/- Activated Twenty Twenty-Three theme
- Active plugins: Forminator, Jetpack, WooCommerce, Wordfence Security
- Deactivated all other plugins
Without Conflict Test
https://gtmetrix.com/reports/staging2.oohlalazouk.com/vUEy630C/- Active Porto theme
- All plugins activated
Thanks,
JulianHey Nithin – WPMU DEV Support (@wpmudevsupport11)
I haven’t forgotten about you; I’ll do the conflict testing and provide the GTMetrix waterfall results in a couple of days.
Best Regards,
JulianHey?Luis – WPMU DEV Support?(@wpmudev-support7)
Sorry, I forgot my GTMetrix account is set to private!
I’m with SiteGround hosting and I’ve already reached out to their support about this issue on 2 separate occasions already. As expected, they say their hosting is working perfectly and blame the theme or plugins for Slow processing?AJAX and REST-API calls.
Looks like I’m out of luck. Not to worry, I’ll have to look for other form plugins.
Thanks for your help!
JulianHey Luis – WPMU DEV Support (@wpmudev-support7)
I followed your Dev Tools suggestion, tested the site over several days and I cannot identify anything that may delay the form submission. I’m no expert of course, so I’m limited in that regard whereas the trained eye would see things I cannot.
I delete the server and browser cache but the problem is always the same.
If you’re interested, you might want to look at the waterfall:
https://gtmetrix.com/reports/oohlalazouk.com/JUvOWhGL/
Cheers,
JulianHey Adam – WPMU DEV Support (@wpmudev-support8)
I reached out to Siteground support and got the usual runaround blaming plugin conflict or MySQL queries for the slow AJAX and REST-API calls processing.
I reached out to Siteground support a second day hoping to get someone else to look at the problem but true to form, I got the same response from a different support officer. So, no luck as expected.
As for differences between the live and staging sites:
Staging site has: CRON disabled Dynamic Caching disabled
Which doesn’t make sense to me because in my mind, disabling CRON and Dynamic Caching should make the staging site slower, not faster than my live site.
What do you think, Adam?
Forum: Fixing WordPress
In reply to: mailto links – Custom Subject and BodyHey threadi (@threadi)
BIG thanks for your help, I appreciate your time and effort to figure this out.
With a bit of tinkering, I was able to get the shortcode to work. I now have the product title in the email subject and the product URL in the email body.
PerfectHere is the final Snippet
/* shortcode to get product title */ add_shortcode( 'custom_mailto_title', 'custom_mailto_title' ); function custom_mailto_title( $atts ) { return esc_attr( get_the_title( get_the_ID() ) ); } /* shortcode to get product URL */ add_shortcode( 'custom_mailto_link', 'custom_mailto_link' ); function custom_mailto_link( $atts ) { return esc_attr( get_permalink( get_the_ID() ) ); }
Here is the mailto link
<p>Don't have time right now? <a target="_blank" href="mailto:?subject=[custom_mailto_title]&body=[custom_mailto_link]" rel="noopener noreferrer">Email this to me</a></p>
I add the mailto link into the product description.
Hey Joshua?@wfjoshc,
Thanks for your help, I appreciate your time and effort.
I run Jetpack on my site so I need to keep xmlrpc.php running.
All the best,
JulianHey Joshua @wfjoshc
My server is using Apache and Nginx as a reverse proxy. So then , the Wordfence auto_prepend file initialization?can be placed anywhere in the .htaccess file, even at the end. Is that right?
Security Threat
One other thing, does Wordfence protect against:
Unauthenticated Blind SSRF via DNS RebindingI’m asking because I see this warning in WordPress Admin >> Tools >Status
And the warning says there is no known protection.
Cheers,
JulianHi Patrick @wpmudevsupport12
Thanks for your concern 😃
The staging site surprisingly performs better than the live site. Please see server values below.
Live Site
Live Site PHP version 8.0.27 PHP Memory limit 2048M WP_MEMORY_LIMIT 2048M WP_MAX_MEMORY_LIMIT 2048M Max execution time 120 Max input time 120 WordPress version 6.1.1
Staging Site
Staging Site PHP version 7.4.33 PHP Memory limit 2048M WP_MEMORY_LIMIT 2048M WP_MAX_MEMORY_LIMIT 2048M Max execution time 120 Max input time 120 WordPress version 6.1.1
Forum: Fixing WordPress
In reply to: mailto links – Custom Subject and Body