lavignechris
Forum Replies Created
-
In case someone else finds this issue, for me with the same problem, the cultprit was under Advanced Settings -> Network, my authentication method was removed and I needed to reset it after updating.
For developers, having a silent error like this was very frustrating as there were no messages or logs to debug.
Forum: Plugins
In reply to: [WooCommerce] e_error WooCommerce plugin update broke the siteI am having this issue as well after updating WooCommerce to 8.3.1. In my case it was due to pushing the 8.3.1 files to the website without doing the update via the dashboard Plugins interface. Having the files for 8.3.1 on the site caused this error. I resolved by reloading the 8.2 files and then doing the update through the dashboard.
Forum: Plugins
In reply to: [Font Awesome] FFont Awesome plugin is broken@mlwilkerson new version fixes the problem for me. thank you for your work
Forum: Plugins
In reply to: [Font Awesome] FFont Awesome plugin is broken@mlwilkerson I have been able to test today.
Added fortawesome/wordpress-fontawesome via composer. I moved it manually into WordPress plugins folder (I’m using the wpackagist service to fetch plugins normally).
The dev version of the plugin that you provided works perfectly from my testing. No errors on the settings page. Inserting icons via shortcodes or via the inline editing tool works as expected.
From my end, all looks good.
Forum: Plugins
In reply to: [Font Awesome] FFont Awesome plugin is broken@mlwilkerson I can test as well
Forum: Plugins
In reply to: [Font Awesome] FFont Awesome plugin is brokenI have this same error and can add some information:
I am running WordPress with composer and therefore I do not use /wp-content/plugins as the plugins folder. It looks like this is the problem as I get a browser console error saying there is a 404 for the css files because the site wants to load them from /wp-content/plugins/font-awesome which for my site, is not correct
This happens from the Font Awesome settings page, for example.
I can fix by changing all of the paths in font-awesome/admin/build/asset-manifest.json from “wp-content/plugins” to my plugins path.
I guess the path in this manifest file cannot be hardcoded as lots of people run WordPress without using the standard “wp-content/plugins” folder path.
Forum: Plugins
In reply to: [Simply Youtube] [Plugin: Simply Youtube] errorLine 83 of simply-youtube.php is incorrect and needs to be updated to:
for( $j=0; $j < count( $uploads ); $j++ ):Right now, it’s set to $j=1 which means it’s skipping the first video.