creativ3y3

Hi, unfortunately it’s installed locally so can’t send a link. It’s just simply the calendar filed on the front end doesn’t show a year or a way to move back in “years” so if you wanted to make the date say for a birthday year, you would have to scroll back 20 years in one month increments at a time for example.

Thanks for getting back. I think i have got to the bottom of it. It seems it was not affecting any other preview on any other plugin or native posts on the site for whatever reason, but it looks like it could be a conflict with a theme plugin causing the issue. If i deactivate that conflicting plugin things work as expected. I will reach out to them and see what they say.

The rollback issue was a separate issue it turns out. WP Rollback released a further update that resolved it.

No problem, understood. As a generic question relating to the structure of wordpress files and child themes, if the single.php template is able to be used in a child theme (by say copying it into the child theme folder). Does this “over-ride” the existing one in the theme, meaning if the theme single.php file gets updated the child one wont? Where if you can do it by plugin or child functions.php it would’nt over-ride the whole file as such…

Hi, it turned out the issue was indeed with the WHERE clause. I got it working when I moved the AND address2…. into the ON clause. Using an endpoint, I wanted compare the lat long info with that provided by a mobile app then to bring back the correct shop information back to present it inside the app.

The solution here resolved my issue:

https://ww.wp.xz.cn/support/topic/siteground-optimizer-v6-and-6g-blacklist-firewall/#post-15054166

Hi Is there a work around similar to the below to allow 6g functionality to be reinstated without the conflict?

https://ww.wp.xz.cn/support/topic/6g-rules-block-cloudflare-plugin-javascript/#post-11650217

Hi @mkarimzada, thanks for your thoughts, I will give that a try. I think you’re right it does seem to activate the field if updated at that point of inserting the post. Think on that basis I will need to loop through all the fields that are acf within the post and update them at this point. Since I’m looking to keep these fields blank or at “default state” I guess my values would have to reflect that. Hopefully by doing that it would “activate the fields” allowing me to update the fields at a later stage after some user interaction on the front end and with no requirement to save on the back end.

Thanks again, this helps, I will give it a try.

Hi Any further thoughts on how to resolve?