i’m using BNFW and i’m encountering an issue with the formatting of the [post_date] Shortcode.
It renders the Date witha mixture of english and german formatting.
Resulting in something like: 11. March 2025 7:35
The Date formatting in WordPress itself is correct.
Expected would be the output of 11. M?rz 2025 7:35
Any hint would be highly appreciated.
Best
Frank ]]>
first thank you, its really a great plugin with a lot of features in the free version and I have already bought 5 add ons from your website (e.g. location map).
I would like to know, how I can center the output of a list with “template=default”. I tried with “<center>” and “</center>” but had no success. The standard alignment seems to be “right”.
Thank you 
My current approach is to add 4 fields, “discount_description”, “discount_code”, “discount_expiry_date”, “discount_active”, and then somehow filter the post_meta before it is output so as to not publish any of these fields in the final post if the discount_expiry_date has been passed or the discount_active is false.
My guess is that I need to make a custom shortcode for the output or to somehow hook into the gd_post_meta shortcode, but I’m not entirely sure how to go about this as I can’t find enough information in the GeoDirectory documentation or by searching the code to help me determine how to tap into it or what object to modify if anything.
I have the Code Snippets plugin installed. Any help would be much appreciated.
]]># foreach() receiving null values in getOutput method of Output.php
# Details
I'm getting an exception error reported by sentry saying that a foreach statement in getOutput method of popular posts is receiving null values. The stack trace is:
**"ErrorException: Warning: foreach() argument must be of type array|object, null given"**
The line it is referring to is foreach( $body->childNodes as $node ) { which is line 181 of web/app/plugins/wordpress-popular-posts/src/Output.php, in the getOutput method. Here is the full code in context for the public function getOutput that this line is inside of:
foreach( $body->childNodes as $node ) {
$clean_html .= $dom->saveHTML($node);
}
So far there appear to be no problems on the site itself, even on the page sentry is reporting that it is finding the error on. However, I wanted to investigate this issue before it became a larger problem.
Wordpress version 6.4.3
PHP version 8.0.22
Plugin version 6.4.2
# Solution
I was considering a defensive programming solution where I might check if the array?is_empy??prior to the foreach, but since this is inside of a plugin, the only way can think to do that on my end is to create a patch. However, if a solution is already known for this issue or if patching would be overkill when there is a simpler solution, I would appreciate any assistance.
]]>I am using CF7 and I tried several different things to get it to work as intended.
I am also using conditional fields.
I have a really long form with several conditions in there, right now if people select a condition it means 33% of the form will show up, 66% stays hidden.
However, in the PDF right now it’s like this:
Name: [your-name]
This means if someone would not fill in the field, in the PDF it will still say
Name:
I am trying to make it so if someone leaves a field empty, it does not just remove the [your-name] but also the text before it in the PDF that indicates what the question was.
I have tried:
– Not using a placeholder, instead use the <label> element and normal text inside the label.
– Using the <Label for= method
There seems to be no way to output the entire <label>…</label> into the PDF
This would be very handy since then if the field is left empty and it’s excluded from the output, it exludes the entire label including the part that says ‘Name:’.
And this way you are not left with a PDF that is filled with empty fields that were hidden under the conditional fields.
Does anyone have a suggestion on how to make this work?
Making all the fields mandatory is not an option, they are not able to fill out the fields hidden under the non-selected conditions.
]]>
I’ve been using <?php the_field(‘field_name’); ?> to retrieve fields. If I change this to: <?php echo wp_kses_post( get_field(‘field_name’) ); ?> does this do the trick?
Additionally, I purchased the ACF Repeater plugin add-on many years ago and am still using it in combination with ACF on a number of old websites. Is the Repeater plugin going to continue to work after this update?
Thanks for your help!
]]>Maybe it can take a while to answer but on the other hand I like that it has the seconds counter (i.e. the chatbot is thinking what to answer so the user waits quietly).
My doubt is if it spends much more per token on the usability of the site on the OpenAI platform, I notice that maybe it spends a little more than when I was running it on google colab, but I understand that there is a lot of back and forth between servers.
I want to collect interactions with users. That’s in the Pro version right?
Thanks 
You’re plugin is really amazing! But I have one little problem. In my XML I need date range for my export. I export orders for yesterday (every day) and I need something like that in the beggining of XML: <OrdersForPeriod from=”{date_From}” to=”{date_to}”/>
I was trying to write few functions but everytime I’m getting error. Is possible to achive something like that?
]]>Warning: Cannot modify header information - headers already sent by (output started at /home1/demo/public_html/billing/wp-content/plugins/hblpay-payment-gateway-for-woocommerce/hblpay-paymentgateway-woocommerce.php:1) in /home1/demo/public_html/billing/wp-admin/includes/misc.php on line 1416
Warning: Cannot modify header information - headers already sent by (output started at /home1/demo/public_html/billing/wp-content/plugins/hblpay-payment-gateway-for-woocommerce/hblpay-paymentgateway-woocommerce.php:1) in /home1/demo/public_html/billing/wp-includes/functions.php on line 6865
Warning: Cannot modify header information - headers already sent by (output started at /home1/demo/public_html/billing/wp-content/plugins/hblpay-payment-gateway-for-woocommerce/hblpay-paymentgateway-woocommerce.php:1) in /home1/demo/public_html/billing/wp-admin/admin-header.php on line 9
]]>