deepwaterpixel
Forum Replies Created
-
Forum: Plugins
In reply to: [Elementor Website Builder - more than just a page builder] JS error@miloss84 I am sorry, but that is an unacceptable response. We are not obligated to submit issues to your GitHub, it is you who is obligated to provide support for issues in your free plugins, right here.
This query is submitted in the correct location, the problem has been well-defined and the solution has basically been handed to you. Ignoring this is very discouraging to the spirit of community engagement here in the support forums, as you are being given this information for free to improve your product. As stated by @neo2k23 , it is unlikely they will report any further issues they find to you here, as clearly outlined by policy.
While this does not seem important to Elementor, it constitutes a violation of the WordPress Plugin Repository Policy, and I have reported this plugin for violating it and have referenced this thread in my report.
- This reply was modified 1 month ago by deepwaterpixel.
Forum: Plugins
In reply to: [Elementor Website Builder - more than just a page builder] JS errorGood, you should not have gone anywhere else — they have an obligation to provide support here in the plugin repository for their free plugin, based on the very policy they so glibly referenced when stating (erroneously and hilariously confidently) that you were an Elementor One user. If they do not wish to provide that support here by incorrectly routing to their support system, well, as taken from the Developer Expectations section of the policy linked above: “Auto-replies and emails that route to a support system are not permitted as they historically prevent humans from addressing emails in a timely fashion.”
Applicable remedies as detailed by that policy are:
- disable or remove any plugin from the directory, even for reasons not explicitly covered by the guidelines.
- remove developer access to a plugin in lieu of a new, active, developer.
- make changes to a plugin, without developer consent, in the interest of public safety.
So, WordPress can fix this for us by removing the plugin, removing Elementor’s developer access, or amending the plugin themselves to remove this error.
Elementor is allowed to promote their paid features, but critically, they are not allowed to degrade the free experience while doing said promotion. The squeaky wheel gets the grease so I made sure to +1 on this and confirm this is a free plugin problem.
What irritates me the most about this is the immediate assumption that because it was their promotional section causing this issue, that you must be a paid user, based on essentially zero work on their end to make that determination. It’s very concerning and smacks of “just touch the ticket” quantity over quality. I will wax poetic about this every time I see it because it’s a symptom of a much worse state of affairs and that is to monetize to no end.
Every company can’t have every dollar. If they want to use the plugin repo as a means to get people using the product for free so they’re willing to pay for Pro, then they need to follow the rules like everyone else.
Forum: Plugins
In reply to: [Elementor Website Builder - more than just a page builder] JS errorThis problem exists in the free version of Elementor and I found it on my sites as well. Please fix this error, do not redirect me to other support or forums, thanks.
Forum: Plugins
In reply to: [Intuitive Custom Post Order] Taxonomy Order Not SavingPlease note, I’ve started seeing this issue with other custom post order plugins. I had this issue with SCPOrder, Real Custom Post Order, and then with this one. Something must have changed in WordPress that causes this, but I can confirm that @greenya’s change does fix the failure to save sorting.
@gishua, if you had a PHP error, then you likely did not replace the code correctly. I commented lines 757 & 758, then added greenya’s code, saved, and reloaded and it worked immediately. I’m glad I found this thread because I would have ended up writing this myself but I’m tired and so grateful to greenya’s help.
@hijiri — update your plugin and you’ll be the only one that works on any of my sites! Please make this minor change and you’ll get dozens of new installs from me 🙂
Forum: Plugins
In reply to: [LH Archived Post Status] Conflict w/ Advanced Ads pluginI just wanted to hop back in and confirm the issue is fixed for me in the v3.02 update. Thank you for resolving this so quickly, it came at a bad time and your promptness really saved me from having to explain the issue or deal with it through the client.
Forum: Plugins
In reply to: [LH Archived Post Status] Conflict w/ Advanced Ads pluginHello, I just wanted to chime in and say that this missing Publishing meta box problem also affects WooCommerce Memberships post type (wc_membership_plan), so I have been forced to add it to the array at
lh-archived-post-status.php:90to try get things working again. It doesn’t seem to work. I have to disable the plugin to make changes, then re-enable it to allow it to work on the existing posts that have already been archived.- This reply was modified 4 years ago by deepwaterpixel.
Forum: Plugins
In reply to: [OoohBoi Steroids for Elementor] I get error message in backendI have encountered this issue with one of the Jet plugins in the past from Crocoblock, and their fix for the 3rd party files was to use a URL replace, like this:
add_filter( 'cherry_core_base_url', 'jet_fix_framework_url' ); add_filter( 'cx_include_module_url', 'jet_fix_framework_url' ); function jet_fix_framework_url( $url ) { return str_replace( 'www/wp-content', 'wp-content', $url ); }Rather than wait on them to fix it (who knows when that will be), you can address it this way in the short term and get this terribly annoying issue fixed in your plugin in the short term. Then, when they fix it, it will continue to work because the
www/wp-contentvalue won’t be returned any more and won’t be picked up bystr_replace().What do you think about this solution?