cosbe
Forum Replies Created
-
I am pretty sure you don’t fathom the possibility that you have a bug and your banner simply won’t want to go away, no matter what I’ve chosen, yes, later, or nah. So please fix it fast or I will uninstall and delete. It is way too annoying to be hunted by this harassing banner on each and every page in the admin. May I point to the fact that this is the only banner that does that thing. And it seems that others are experiencing the same issue, reason why they also have given one star. Wouldn’t be simpler to simply remove this bit of code and behavior from this plugin with an update? You may also consider that not all of us love yet another cookie.
No, “nah” or even “yes” won’t work for me either. So I also reviewed this with 1 star, because is the only banner that aggressively hunts me on every single page in admin. Next will be uninstall and delete. Too bad, because otherwise it works well.
Please fix or give up to this nonsense not-working method of getting feedback.
Forum: Plugins
In reply to: [LiteSpeed Cache] Customize 403 pageI understand the security concern. You are right. And the complexity of customization. But this last one, I think, should be allowed as long as this message is served under the owner’s domain… I mean, at minimal, at least a custom message should be allowed, and no CDN logo. Unless this is a form of advertising… But then again, to whom to advertise? To those who are actually intending of breaching the security?! Just thoughts.
Anyway, thank you for your support! I hope this gets an echo somewhere.
Forum: Plugins
In reply to: [LiteSpeed Cache] Customize 403 pageI really don’t see the sense in putting a CDN logo on someone else’s domain. What is the point in doing that, or prevent redirecting and customization?
I really hope that this gets changed.
Please send this to the decision making team, if it is not too much to ask.
Thank you for your support.
Forum: Plugins
In reply to: [LiteSpeed Cache] Customize 403 pageIt is obviously the one on the quic.cloud I am referring to since it contains the QC logo. So, hmm, it is not nice, since the 403 forbidden error refers to a domain of mine, which is also shown in the address bar on the browser. Can I hope for a change here? Customize or redirect this?
Forum: Plugins
In reply to: [LiteSpeed Cache] Customize 403 pageWhen traffic is restricted at Quic.cloud CDN level, a 403 page with Quic.cloud logo is shown for blocked incoming visitors. I was asking about either customizing that page to display a custom logo and content instead, or to be able to perform a redirect to a different page or domain.
Hi @miemie
Thank you for the quick reply. I reinstalled the plugin and reconfigured it and now it seems to work as intended. I will monitor it and if this repeats I will report it. But for now, it seems fixed.
Thank you!
Hi Josh,
I have searched and did NOT find any email responses regarding the issue I raised two times in your paid support ticket system. Neither in email folders nor in Spam.
I have a pre-purchase email response originated 12/7/2019 from support@wholesalesuiteplugin.com after asking if the WOOCS is specifically supported by your plugin, to which I received the response that is not. I initiated this conversation from your Contact Form.
I also opened a ticket on 12/16/2019 where I suggested an improvement for displaying the percentage of the WS price next to the price and also received an email responding that the request “was sent to developers for review. However, we can’t guarantee an ETA for this”.
Aside from this communication I only received marketing emails from you, including the one inviting me to renew the subscription for “support” two days ago.
I also have two emails originated yesterday and today from the same email address mentioned above, as a response to my public rating and feedback which drew your attention. You indicate there two screenshots with responses I have never received. As I said in the first place: they are definitely NOT in my Spam folder and maybe you should verify the way your ticketing system works, as well.
I will take your word for sending them since I do not have the email responses on my side.
Now you see how soft requests seem to pass through to you during the first year of paid support subscription and I did receive a response to them. However, the bug reports regarding the cart displaying wrong numbers for WOOCS converted currencies for which I raised two tickets, somehow never reach me with a response.
By the way, after opening these two consecutive bug-reporting tickets I DID receive the automated confirmation email, so the “spam magnet” argument for your responses seems thin.
The rating came from frustration, obviously. It is this feeling that you simply don’t want to respond to support tickets in a system that you, kind of, lead people to pay for, including here in the forum. I’ve seen several times how you tell people to open a ticket (of course, they have to pay for that support) for their questions. I understand that support may be valuable and a business model for you, but you must also be sure it works. Both ways.
I have checked now the integration with WOOCS (which was deactivated so far) and indeed it works now, so thank you for solving this, at least.
Regards,
C. B.
- This reply was modified 5 years, 5 months ago by cosbe.
You might be right. Just coming from the WPSSO/Google Web-Stories issues and latest updates I wrongly assumed it was this Core the error refers to. My apologies.
Oh, it was just the Querry Monitor which indicated the Core as the trigger. Interestingly, that only happened once. A subsequent login/logout did not trigger the error again. Maybe it was a glitch of some sort…
May I add, all of the above-mentioned plugins have reported fatal errors. Recovery Mode initiated and I deactivated them all to restart the website. Not nice.
Forum: Plugins
In reply to: [Web Stories] Cannot visualize/preview the web story@jsmoriss I updated the Strip Microdata plugin following your resolve and the website crashed altogether:
Fatal error: Uncaught Error: Too few arguments to function WpssoSsm::init_objects(), 1 passed in /....../wp-includes/class-wp-hook.php on line 287 and exactly 3 expected in /......./wp-content/plugins/wpsso-strip-schema-microdata/wpsso-strip-schema-microdata.php on line 69 Call stack: WpssoSsm::init_objects() wp-includes/class-wp-hook.php:287 WP_Hook::apply_filters() wp-includes/class-wp-hook.php:311 WP_Hook::do_action() wp-includes/plugin.php:478 do_action() wp-content/plugins/wpsso/wpsso.php:457 Wpsso::set_objects() wp-includes/class-wp-hook.php:287 WP_Hook::apply_filters() wp-includes/class-wp-hook.php:311 WP_Hook::do_action() wp-includes/plugin.php:478 do_action() wp-settings.php:546 require_once() /....../wp-config.php:75 require_once() wp-load.php:42 require_once() wp-admin/admin.php:34 require_once() wp-admin/plugins.php:10Now what?!…
Forum: Plugins
In reply to: [Web Stories] Cannot visualize/preview the web story@jsmoriss Understood. But I kinda like the stories now, and I want to keep it live. Will I miss the Strip Microdata?
@luckynasan Could these two plugins live together at some point?Thank you all for your support!
Forum: Plugins
In reply to: [Web Stories] Suggestion: Add Close Story button pointing to story archivesIf there is a Play/Pause button I don’t see why there should be a more complicated swiping way of returning to the archive. I hope they will implement a straight forward way of navigation at some point.
Thank you for your support!
Forum: Plugins
In reply to: [Web Stories] Cannot visualize/preview the web story@jsmoriss I confirm that deactivating only the WPSSO Strip Schema Microdata made the story visible! Can we hope for a fix?
@luckynasan Thank you!