invision-studios
Forum Replies Created
-
Forum: Plugins
In reply to: [Clover Payments for WooCommerce] V 2.0 is BROKEN for ElementorThanks for making this update. Greatly appreciated.
Forum: Plugins
In reply to: [Clover Payments for WooCommerce] V 2.0 is BROKEN for Elementor@fitwd I did exactly what you did – disable the Classic Editor plugin (to enable Gutenberg). By re-authenticate I mean regenerating a new API code on the Clover site. I tried to convince the client to switch back to Stripe but he wants to collect all sales into a single merchant account. He uses Clover for his brick and mortar business.
Sounds like Clover just didn’t do any research before they decided to “upgrade.” Still, the biggest sin, is forcing the auto-update on everyone.
Forum: Plugins
In reply to: [Clover Payments for WooCommerce] V 2.0 is BROKEN for ElementorI asked ChatGPT to give me stats on page builders. Elementor is apparently used almost twice as much as Gutenberg, and as ChatGPT says, LEADS THE MARKET.
As of June 2024, the market share of major WordPress page builders is as follows:
- Elementor: 8.83%
- WordPress Block Editor (Gutenberg): 4.94%
- WPBakery: 3.66%
- Divi: 2.16%
- Beaver Builder: 0.41%
- WordPress Site Editor: 0.38%
- SiteOrigin Page Builder: 0.31%
- Oxygen: 0.15%
- Themify Builder: 0.08%
- Thrive Architect: 0.07%
These figures represent the proportion of all websites using each page builder.
It’s noteworthy that Elementor leads the market, with a significant user base.
Forum: Plugins
In reply to: [Clover Payments for WooCommerce] V 2.0 is BROKEN for Elementor@fitwd Somehow I got Clover Payments 2.0 to work with Elementor. All of our sites run on Elementor Pro. We had disabled Gutenberg with a plugin because it’s such a pain. I had to disable that plugin, then re-authenticate Clover; now it’s working fine. Of course the layout changes slightly.
NOTE that just the grey boxes for card info, etc would show up on the checkout page, and not be selectable prior to making this change.
I’m still upset that Clover would push the plugin update automatically and break our websites. At the very least, they could have added a warning that the old plugin was about to be disabled.
Forum: Plugins
In reply to: [Clover Payments for WooCommerce] V 2.0 is BROKEN for ElementorIt’s very short-sighted of Clover to release a plugin that isn’t compatible with the largest page builder plugin in the WordPress universe – Elementor.
It’s unconscionable that you force updates on users and disable the old plugin.
I just restored to the previous version 1.0.12 today, and it is no longer working (but it worked yesterday, prior to the last 2.0 auto push).Forum: Plugins
In reply to: [Plugin for Google Reviews] Google listing not listedI will follow up here AFTER Google approves the updates on the listing. Pretty sure that will solve this.
Forum: Plugins
In reply to: [Plugin for Google Reviews] Google listing not listedIt appears the GMB listing in question is set as a service area business. I think that’s the issue. It’s not showing up in the PlaceID finder at all, but other similar client businesses are.
I just checked the “I also serve customers at my business address. (Your address will be hidden from the public if this box isn’t checked.)” box and will give it a day or two to show up in the PlaceID finder, and try again.
I’m using your plugin on dozens of other sites and always obtain the API code the same way… that’s why I was so baffled. I don’t think it’s your plugin’s fault at all, it’s the local service business aspect hiding the physical address.
My apologies. This is a great plugin, sorry to confuse Google issues with plugin issues.
Forum: Plugins
In reply to: [Plugin for Google Reviews] Google listing not listedI think the developer is using the old Google Places API, not the modern Google Maps API.
Forum: Plugins
In reply to: [Plugin for Google Reviews] Google listing not listedI should mention this is a verified Google My Business listing. The company shows up in Maps with Google autocomplete.
Forum: Fixing WordPress
In reply to: /wp-admin: Sorry, you are not allowed to access this page.I discovered a quick and easy method to resolve this issue. I had installed a new plugin, activated it, and when I went to access the settings I got the error message “Sorry, you are not allowed to access this page” on a blank white screen.
I hit the back button in the browser to return to main admin screen, then went to Settings > Permalinks and just re-saved my permalinks. I believe that re-writes the .htaccess file.
After that, no problemo! YMMV.
Forum: Fixing WordPress
In reply to: I can't insert images into my postsI just discovered that using Sucuri Security plugin’s hardening setting for the wp-content directory prevents insertion of anything into a post — an image, a form, a download… Disabling that feature made all the inserts work again.
Forum: Fixing WordPress
In reply to: Update 4.3 broke Revolution SliderI had the same issue. After updating to 4.3 and the latest version of Rev Slider, text containers on my site became narrow, causing the text to wrap.
What I discovered is that any text that I had applied a custom text style to wasn’t displaying corrected. So I selected individual blocks of text, one by one, and renamed and reapplied styles.
The other thing I had to do to fix this was to resize the text frames in the slide editor (by pulling the right center handle to make the text frame wider than before.
Very strange update.
Forum: Plugins
In reply to: PHP Out of memory errorsMy client’s site is on a dedicated managed server, so that’s not the issue.
We are running a bunch of plugins, including WPML. I suspect it to be the culprit of most of the out of memory errors.
Forum: Plugins
In reply to: PHP Out of memory errorsI’m getting a similar error. I noticed my server is also running PHP 5.3.29. WP recommendation is
“PHP version 5.2.4 or greater (recommended: PHP 5.4 or greater)”Perhaps that is at the root of this issue?
Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] Cannot create folderI can affirm this is the problem. I just migrated an installation to a new domain. Even though I did a search and replace on the database, it apparently didn’t find the file path (because it wasn’t an https://www… path, it was a /home/accoutname/public_html? path).
All working happily again. Thanks for the tip, @swatson.