ldwd
Forum Replies Created
-
@josklever Thank you for your update, that’s very kind 🙂
We’ll be waiting for their fix.We encountered the same issue: updating to 4.4.17 with Mollie Payments for WooCommerce enabled caused a fatal error.
At first we didn’t know what caused it. By disabling all plugins via the database we gained access to the back-end again. While re-enabling the plugins it crashed again on activating Mollie Payments for WooCommerce. Looking in our update history, the last plugin updated before the first crash was Paytium (Mollie’s last update was from a month ago, so that couldn’t be it). Checking this forum I saw similar reports. Reverted back to 4.4.16 and all works fine.
So yes, most definitely there is a conflict with Mollie Payments for WooCommerce 8.1.1.
We use WP 6.9.@djepayne Can you please check and confirm the correct filename? Because in the original files downloaded from ww.wp.xz.cn the file is called
frontend-handlers.asset.php(so with a hyphen and period combined).@femiyb Sorry for the late reply and thank you for the beta version. I tested and the iDEAL page is loading now, no error message. Looking forward to the official update!
Forum: Plugins
In reply to: [Snippet Shortcodes] Free version locked, must upgrade to Premium@aliakro Ah thank you so much! I really appreciate that 😀 Just updated and all shortcodes are editable now. Thanks!
I know we are not supposed to reply with I have the same problem but need to create a new topic according to the forum guide lines… Though I do experience the same problem: payments are not accepted without billing address. Reverting to 7.10.0 resolved the issue.
Forum: Plugins
In reply to: [Pods - Custom Content Types and Fields] How to change the slug of the cptYou can edit the name of the pod in the upper left corner. Then save the pod and refresh the dashboard. When you add a new post of your CPT it will have the new slug.

@qriouslad Ahhh totally missed that! Thanks!
@josevarghese Thanks for your explanation, that really helped me a lot!
I added the snippet below to my functions.php which removes the og:url from one specific page using a filter hook from Yoast SEO plugin:
// Remove Yoast og:url tag
add_filter( 'wpseo_opengraph_url', 'remove_yoast_meta_tag' );
function remove_yoast_meta_tag( $presenter) {
if ( is_page ( 'my_page_slug' ) ) {
return false;
}
return $presenter;
}This results in the url from the address bar being used which contains the parameter as you pointed out.
Now this plugin is even more awesome 😀 Thank you!
@stevejburge I’m very sorry to hear that. The help of the PP team over the past 18 months has been much appreciated.
Your free support may not solve everything, though I do hope my help will solve one of the issues as I sent you detailed bug fixing in this topic. Would you please be willing to implement them until WordPress core has it’s own comments section? Thank you!
@rizaardiyanto Thanks for your investigation so far.
Upgrading to a paid plan for a plugin that doesn’t fully work correctly is not really an option I’m afraid (I’m also still experiencing other bugs I reported before).
Two other users commented on this topic with similar issues, but those comments were removed by a moderator stating that they should start their own topic. In this topic of a third user, notifications are also sent wrongly and a fourth user confirmed this.Therefor I hope you can assist free users as well. Thank you!
@rizaardiyanto There may be a new issue (which is probably not a real issue since it may only happen because of the existing issue). The notification send for the wrong post type now sometimes lacks a user (see screenshot). The notification send for the correct post type (updated by the same user) does show the user.

Please note that the post type here (Ondernemer) was not set in the workflow.
This issue did not occur before. Thought reporting this may help your investigation.
Hi @rizaardiyanto,
Thank you for this new version. I followed all the steps. Unfortunately, the issue still persists (I tested with updating a default page).
Hi @rizaardiyanto,
One contributor updated a post so here is a first update. The issue is partly solved.
The When to notify part is working correctly for now. But the For which content condition is not (always) respected. For instance, I have set up a workflow for When the content is updated with only one post type assigned (Bedrijven (Company)). But the notification is still send when another post type gets updated (Ondernemer (Vendor)).
Good to know: a Vendor post is set as the parent of a Company post. Maybe this information will help you look in the right direction.
Thanks for looking into this!
@rizaardiyanto Thank you for this beta version! I just installed it and will let you know how it works out. I’ll have to wait until a contributor (a type of client on this website) will do an update before I can check if it resolved the issue, so it may take a day or two.