agreenstreet
Forum Replies Created
-
Forum: Plugins
In reply to: [ShareThis Share Buttons] Disable for homepageHi @sharethis ,
Though the question was asked to @bulgariana I wished to contribute our SEO reasons for delaying the execution of ShareThis scripts using the third party WP Rocket optimizer plugin.
The biggest issue is Google Core Web Vitals.
The waterfall with all unncessary scripts delayed from firing until a mouse, tap or scroll action fires them allows our site to get a passing score with Core Web Vitals.
If ShareThis is allowed to fire its script as normal and make multiple calls to the needed outside servers for tracking and counts, this considerabley increases the page size (weight), the number of requests and the time of response as measured by Core Web Vitals.
The speed gain benefit by delaying ShareThis from firing until the page is loaded and interacted with is dramatic. We love the plugin just need to control when it fires to get good grades from Google. If fail on Core Web Vitals your page rank is negatively affected.
Repectfully offered as our reasons for delaying ShareThis script from immediately activating.
Aly
Forum: Plugins
In reply to: [ShareThis Share Buttons] BUG: Include at bottom of page content (checkbox)Hi @sharethis ,
Confirming that I am using the latest version of the plugin 1.5.7.
The problem persists.
With two posts, with near identical PAGE TITLES so SLUGS (URL’s) apart from the last three URL characters, ShareThis confuses itself.
If you turn (on/off) ShareThis on one page, it does the opposite (on/off) on the other page. Oone page ON makes the other page OFF.
Basically I have given up on this one. If you wanted to dig into the issue I have a development server where I could give you cPanel, MySQL Admin & WordPress Admin access so you can see both sides back & frontend.
Let me know if you wish to pursue this or let it go.
Thanks.
AlyForum: Plugins
In reply to: [ShareThis Share Buttons] Disable for homepageHi @bulgariana ,
The solution I am using that allows the deferral of ShareThis.js and other scripts launched by ShareThis is to use WP Rocket WordPress optimization plugin, with the following settings enabled.
OPTIONS
- Minify JavaScript files > Checked (active) > Excluded JavaScript Files > sharethis.js
- Load JavaScript deferred > Checked (active)
THIRD PARTY SOLUTION
This is not a built-in solution from ShareThis but rather it uses the functionality of a third party optimization plugin, WP Rocket, to massively speedup your website by loading pages with JavaScript deferred until an action is taken by the user (click, scroll, tap).Any of these user actions then triggers all deferred JavaScripts to run after the page is loaded, as seen by Google Page Speed Insights (Core Web Vitals).
Basically this functionality bypasses ShareThis, stopping it from loading all the many, many processes and calls to external servers, until you want the script to run. The speed up effect is very significant for reducing load times.
(I would love if ShareThis could build an equivalent run script deferral ability into their plugin in the future)>
Combine this with WP Rocket’s other CSS speed increase abilities and I now have managed to get my two production websites mostly passing Core Web Vitals for mobile & desktop, admittedly after a lot of trial and error optimization work.
SUGGESTION
This is just a suggestion, understanding this it does not directly answer your question, within the ShareThis plugin. A third party workaround but I thought to mention it as a potential solution that is definitely working well.Aly
Forum: Plugins
In reply to: [ShareThis Share Buttons] Plugin is unavailable after installation/activationShareThis 1.5.6
I have the identical issue on two WordPress sites, each using a different theme but hosted on the same VPS (virtual private server).
One site uses the Classic Editor and one the new blocks and widgets, both throw the same critical errors on trying to enter general settings. If I rollback to ShareThis 1.5.5 then I can get into general settings without this error appearing and this has been the temporary workaround.
Will reproduce these errors underneath the configuration information.
WordPress version 5.9.2
### wp-server ###
server_architecture: Linux 2.6.32-954.3.5.lve1.4.80.el6.x86_64 x86_64
httpd_software: Apache
php_version: 7.4.26 64bit
php_sapi: litespeed
max_input_variables: 1000
time_limit: 30
memory_limit: 128M
admin_memory_limit: 256M
max_input_time: -1
upload_max_filesize: 32M
php_post_max_size: 32M
curl_version: 7.71.0 OpenSSL/1.1.1d
suhosin: false
imagick_availability: true
pretty_permalinks: true
htaccess_extra_rules: true### wp-database ###
extension: mysqli
server_version: 5.6.51-cll-lve
client_version: 5.6.51
max_allowed_packet: 268435456
max_connections: 600### wp-plugins-active (16) ###
ACF Content Analysis for Yoast SEO: version: 3.0.1, author: Thomas Kräftner, ViktorFroberg, marol87, pekz0r, angrycreative, Team Yoast, Auto-updates enabled
Advanced Custom Fields: version: 5.12, author: Delicious Brains, Auto-updates enabled
Antispam Bee: version: 2.11.0, author: pluginkollektiv, Auto-updates enabled
Classic Editor: version: 1.6.2, author: WordPress Contributors, Auto-updates enabled
Fluent Forms: version: 4.3.3, author: Contact Form – WPManageNinja LLC, Auto-updates enabled
Imagify: version: 1.10, author: WP Media, Auto-updates enabled
Revive Old Posts: version: 9.0.6, author: revive.social, Auto-updates enabled
ShareThis Share Buttons: version: 1.5.5, author: ShareThis (latest version: 1.5.6), Auto-updates disabled
Shortcoder: version: 5.7, author: Aakash Chakravarthy, Auto-updates enabled
Sucuri Security – Auditing, Malware Scanner and Hardening: version: 1.8.30, author: Sucuri Inc., Auto-updates enabled
Wordfence Security: version: 7.5.8, author: Wordfence, Auto-updates enabled
WP Crontrol: version: 1.12.0, author: John Blackbourn & crontributors, Auto-updates enabledWP Rocket: version: 3.10.8, author: WP Media, Auto-updates disabled
WP Rollback: version: 1.7.1, author: Impress.org, Auto-updates enabled
Yoast Duplicate Post: version: 4.4, author: Enrico Battocchi & Team Yoast, Auto-updates enabled
Yoast SEO: version: 18.3, author: Team Yoast, Auto-updates enabled
## ShareThis Critical Errors ##
Error Details - Site using blocks & widgets ============= An error of type E_ERROR was caused in line 11 of the file /home/wcnp26fmi3kc/public_html/dev.passionforbusiness.com/wp-content/plugins/sharethis-share-buttons/templates/general/general-settings.php. Error message: Uncaught Error: Call to undefined method ShareThisShareButtons\Share_Buttons::randomGif() in /home/wcnp26fmi3kc/public_html/dev.passionforbusiness.com/wp-content/plugins/sharethis-share-buttons/templates/general/general-settings.php:11 Stack trace: #0 /home/wcnp26fmi3kc/public_html/dev.passionforbusiness.com/wp-content/plugins/sharethis-share-buttons/php/class-share-buttons.php(509): include_once() #1 /home/wcnp26fmi3kc/public_html/dev.passionforbusiness.com/wp-includes/class-wp-hook.php(307): ShareThisShareButtons\Share_Buttons->general_settings_display('') #2 /home/wcnp26fmi3kc/public_html/dev.passionforbusiness.com/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array) #3 /home/wcnp26fmi3kc/public_html/dev.passionforbusiness.com/wp-includes/plugin.php(474): WP_Hook->do_action(Array) #4 /home/wcnp26fmi3kc/public_html/dev.passionforbusiness.com/wp-admin/admin.php(259): do_action('toplevel_page_s...') #5 {main} thrownError Details - Site using classic editor ============= An error of type E_ERROR was caused in line 11 of the file /home/wcnp26fmi3kc/public_html/thesuccessalliance.com/wp-content/plugins/sharethis-share-buttons/templates/general/general-settings.php. Error message: Uncaught Error: Call to undefined method ShareThisShareButtons\Share_Buttons::randomGif() in /home/wcnp26fmi3kc/public_html/thesuccessalliance.com/wp-content/plugins/sharethis-share-buttons/templates/general/general-settings.php:11 Stack trace: #0 /home/wcnp26fmi3kc/public_html/thesuccessalliance.com/wp-content/plugins/sharethis-share-buttons/php/class-share-buttons.php(509): include_once() #1 /home/wcnp26fmi3kc/public_html/thesuccessalliance.com/wp-includes/class-wp-hook.php(307): ShareThisShareButtons\Share_Buttons->general_settings_display('') #2 /home/wcnp26fmi3kc/public_html/thesuccessalliance.com/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array) #3 /home/wcnp26fmi3kc/public_html/thesuccessalliance.com/wp-includes/plugin.php(474): WP_Hook->do_action(Array) #4 /home/wcnp26fmi3kc/public_html/thesuccessalliance.com/wp-admin/admin.php(259): do_action('toplevel_page_s...') #5 {main} thrownAlastair
P.S. Have tried uninstalled / reinstalling ShareThis 1.5.6 from scratch and only rolling back to 1.5.5 solves the issue
- This reply was modified 4 years, 3 months ago by agreenstreet.
- This reply was modified 4 years, 3 months ago by agreenstreet.
Forum: Plugins
In reply to: [ShareThis Share Buttons] BUG: Include at bottom of page content (checkbox)Hi @nezemnyashechka ,
The support question has to do with the ShareThis Plugin. This is the WordPress ShareThis Plugin Forum correct?
Here are two screen shots that show what I am referring to.
https://photos.app.goo.gl/Eu2Gzq1AirTCTiy38Screenshot 1 – Shows the two pages in WordPress Edit mode, with the “Include at bottom of the page content” checkboxes selected.
Screenshot 2 – Shows the backend MySQL database table & fields referred to in my last message.
Basically if you keep the PAGE TITLES identical “Free Video Tutorial”, even though the pages are two different posts, ShareThis won’t keep the “Include at bottom of page content” checkbox value blank for both pages It keeps filling out the checkbox.
The only fix I found was to name the PAGE TITLES differently, then it works.
This appears to be a bug or user interface issue to my mind. The immediate problem is fixed, by renaming one of the PAGE TITLES to be different, but I am reporting this behavior as a potential bug to the developer.
Maybe I am misunderstanding how this should work but not keeping/saving a setting seems like an issue.
Alastair
Forum: Plugins
In reply to: [Pre* Party Resource Hints] Preload on per-page basisHi @samperrow
I would be very interested in the updated plugin that allows preloading of fonts and other resources on a page-by-page basis. Trying to meet Google’s new Core Web Vitals (page-by-page).
Alastair
Forum: Plugins
In reply to: [Contact Form 7] Lazyload Recaptcha jsHi @joshwebfx
You read my mind, I have been playing with exactly the same issue for the same reasons these last few hours, except CF7 5.4 isn’t submitting at all on one our sites, using WP Rocket with deferred script load but it is on the other…
It is just too much work to figure this out.
Sadly I think I am giving up on CF7 and moving over to Fluent Forms. Fluent Forms still gives reCaptcha v2 support in-built, a form database saving copies of submitted forms and no JS & CSS code on pages that aren’t form pages, which helps the load speed optimization without needing Asset Cleanup Pro plugin to remove the scripts. Plus I don’t need Flamingo as a separate DB storage plugin and it works with WP Rocket.
My move is based on a recommendation from a page load speed expert for the above advantages.
Hopefully you can soon find a solution to do what you need with CF7. The plugin has been great for us for many years now and I just want to thank the plugin designer for the value and benefit that has been generously given, I am grateful.
For us its time to move on for all in one, no unnecessary code on non-form pages and a working integration with WP Rocket for better page load speed. Everyone’s situation and needs are different. These are my reasons for changing.
Wishing you a quick solution.
Aly
I was able to get Flying Scripts working with Cache Enabler successfully, I can see the changes in the code. The difference here is I also have the Autoptimize plugin installed.
So I am thinking Flying Scripts interacts correctly with Autoptimize to insert the script delay code, which is then cached by Cache Enabler. With this 1/2 arrangement Flying Scripts appears to be working just fine with Cache Enabler.
Hadn’t realized it didn’t work with Cache Enabler until I read this thread!
Hoping this helps.
Aly- This reply was modified 5 years, 4 months ago by agreenstreet.
OK I figured out how to reapply the API key copying and pasting via manual activation from Sucuri’s firewall settings, my mistake.
However on successful application of the API key linking to Sucuri’s firewall the Sucuri Plugin immediately gives the error message that started this thread.
“SUCURI: Log file not found.; this generally happens when you use an invalid API key, or when the connection with the API service suddently closes.”
The local log files were deleted (see previous post) after the plugin was uninstalled. Upon reinstallation of the plugin and recreation of the log file, plus activation of the API allowing the sending of local to server log files, the error occurs.
Aly
Hi There,
I am receiving the same error as @neotechnomad on all my sites, three installations.
Tried uninstalling the plugin and manually deleting all /wp-content/sucuri/… files to clean house. The log file is recreated and locally stores the entries but is unable to send the log file to Sucuri due to a missing API key.
Missing API Key Issue:
General Settings Tab > API Key > Recover via E-mailOn attempting to recover the API key via e-mail, the plugin attempts, refreshes the screen and logs a “API key recovery (failure)”.
API Service Communication Tab > API Service Communication shows green (enabled) to https://wordpress.sucuri.net/api/
Generating an API key fails as well giving the error “SUCURI: Unable to store event (dir error).”
So you cannot recover or generate a new API key for the plugin to send the local log files to the Sucuri server.
Help please.
Aly
Hi @wfadam ,
Sounds like some good advice re: the table structure defaults.
Thanks for the explanation and suggestions, please consider this closed as there is no definitive way for me to confirm what caused the issue.
Have a great day.
Alastair
Hi @wfadam ,
Thank you for the reply.
Looking at phpMyAdmin backend for the table types, I see all of the tables set to MyISAM except for the following set to InnoDB:
wp_options
wp_popularpostsdata
wp_popularpostssummary
wp_wfls_2fa_secrets
wp_wfls_settingsI cannot tell at this stage what the original table formats would have been prior to the database restore. Would the MySQL dump command not save the existing table formats and recreate them upon a restore without changing table types?
Your suggested explanation may well explain the issue.
Would you recommend changing all the table types over to InnoDB?
Thanks.
Alastair
- This reply was modified 5 years, 9 months ago by agreenstreet.
Forum: Plugins
In reply to: [Contact Form 7] wpcf7-validation-errors alert-warningForum: Plugins
In reply to: [Contact Form 7] wpcf7-validation-errors alert-warning@wporgspix
@edebe2OK have found the answer, at least for one of our installs.
Plugin conflict with Bootstrap for Contact Form 7 causes the issue.
This plugin hasn’t been updated for a while and I’m guessing won’t be so I will have to replicate the changes it is making manually using the style.css sheet and see if I can avoid the code conflict.
On my other site that doesn’t use Bootstrap I haven’t yet figured things out.
Hope this helps you both or at least gives you a clue.
Aly
Forum: Plugins
In reply to: [Contact Form 7] wpcf7-validation-errors alert-warning@wporgspix
@edebe2OK the older site has a different CF7 table structure and the newer site does not contain these tables holding CF7 submission data.
wp_cf7dbplugin_st
wp_cf7dbplugin_submitsDo your problem sites contain these tables?
Aly