FGD
Forum Replies Created
-
Forum: Plugins
In reply to: [Simnor Shortcodes] Can't close the accordionThank you Captramrod01.
That makes it close and not reopen but the minus icon still shows (that has to do with the css.) And, if this plugin gets updated, the client will have to repeat these steps.
Forum: Plugins
In reply to: [Simnor Shortcodes] Can't close the accordionAny luck with this?
Is there any way to make the expanded div close when it is clicked?
The information above is not really making sense. Surely there is a way to add some script into the header or footer of the website to allow for this functionality without editing the Plugin files.
Thanks.
Forum: Plugins
In reply to: [WooCommerce] Cannot access wp-admin after updating to 2.2.9Also, just to note. Not sure if it was this plugin that caused my White Screen in the WordPress Admin. At the same time of update, I updated the Yoast Google Analytics Plugin. See thread here – https://www.ads-software.com/support/topic/cant-access-wp-admin-after-latest-update?replies=3#post-6337649
The way I found this issue is because the plugin caused errors when attempting to reactivate.
May be worth looking into for this thread too!
I was blaming another plugin update to my white admin pages (WooCommerce) but after further trouble shooting, it appears to be this plugin. Rolled back to 5.2.4 and it is working again.
Forum: Plugins
In reply to: [WooCommerce] Cannot access wp-admin after updating to 2.2.9OK. I got everything working again (and with the new 2.2.9.) Here are my steps to resolve.
1.) Renamed the plugins folder via ftp.
2.) Logged into admin and navigated to the plugins page (to deactivate the plugins.)
3.) Renamed the plugins folder back to plugins.
4.) Went back to the plugins to reactivate them.
5.) Deactivated WooCommerce 2.2.8 (remember I rolled back on my earlier comment.)
6.) Updated to WooCommerce 2.2.9 and reactivated.
7.) Everything works again.Hope this helps!
Forum: Plugins
In reply to: [WooCommerce] Cannot access wp-admin after updating to 2.2.9Same here too. Rolled back to 2.2.8 to see if that would help. Nope. I’m still in the process of troubleshooting. Also, on the front end, the price is not displayed and just shows a spinning icon. We are using Gravity Forms to display product options.
OK. I found the solution to the old calendars showing up for us. Unfortunately, it will be a long and painful road to get everything restored. Here is the process:
1.) Export your Google Calendars.
2.) Unshare and rename for current Google Calendars. We added (discontinued GAPIv2) to the end of ours. So that we can know the difference.
3.) Create a new Google Calendar. Share it with the Public.
4.) Import your ICS file that you exported in step 1.
5.) Create a new GCAL feed in your WordPress website.I hope this helps others.
I created a brand-new public Google calendar. Added an event. Created a new GCAL event feed and this is what I get. “Some data was retrieved, but could not be parsed successfully. Please ensure your feed settings are correct.
No events to display.”Still broken for me. And I too am using Google Apps for Business with a custom domain.
(Calendar ID: [email protected])
Forum: Plugins
In reply to: [Simple Calendar - Google Calendar Plugin] Not working after update 2.1.0Not working here either. Since the API issue, I was forced to update. Tried my own API key, tried creating a new shared calendar, tried creating a new feed. Nothing. Try to click the next button on the calendar view and receive a “Request has failed.”
Same here. Broke the front-end of the website and the admin of the website. They just show a blank screen. Rolled back to 4.6.1.1 and all is good again.
Just updated to version 2.0.6 and the same issue. Rolling back to 2.0.3.1 and all is good again.
Forum: Plugins
In reply to: [Simple Ads Manager] Ads keep dissappearingI tried upgrading to the newest version 2.4.91 and the ads continue to disappear. Rolling back again to 2.3.85 and all is good again.
UPDATE: Just tried to update to 2.0.5 (from 2.0.3.1) and all my feeds say – No events to display. I guess I will stick with 2.0.3.1 since everything is working as it should. We have way too many feeds to go back and re-do them all. It would take days.
Update
I just deactivated the plugin and deleted it from the site. Went and re-downloaded and installed a new blank copy and activated it and I am not getting the error. So, it must have been some customization that was not compatible after the newer WordPress and Woocommerce installations. I will mark this a solved for now but will keep an eye out if I find the conflict as I re-customize from scratch.
Thanks.