nickberens360

Yep, having the same problem here.
https://www.fdlunitedway.org/board-of-directors/

@dcooney ok thanks for the heads up.

• This reply was modified 3 years, 8 months ago by nickberens360.

@dcooney Ha, totally overlooked that. Thanks!

Link: https://gnomegamesv2.temp927.kinsta.cloud/shop/

@maartenbelmans thanks for the quick response. So should I remove just the meta_value values or remove the entire record? Thanks

Hi @maartenbelmans I just reached out to the person that put the site together. They do not know the amount of fields they added but said it was around 10-15. They said they created the fields from the Edit Products Screen. We are using this your plugin on several of our sites and a couple of them are experiencing the same error. Thanks in advance for your help!!

I believe the site with the error was cloned from another site using the plugin. Could that be the issue?

update wp_posts set menu_order=0 where post_type=’product’

Hey, thanks for the fast response. that worked. great plugin btw!

• This reply was modified 4 years, 7 months ago by nickberens360.

@munirkamal There is no need to define a save point unless you want to save to a custom location. From the acf local json documentation:

Getting started
To start using the local JSON feature, simply create a new folder in your theme and name it acf-json. This folder must have permissions for the server to read and write (in most cases 755 will work well).

Once this folder exists, each time you save a field group a JSON file will be created (or updated) with the field group and field settings. The JSON file will be named using the field group’s unique key.

Now that the JSON file exists, ACF will load the relevant field group and field settings from this file which reduces the number of database calls during your page load!

As you can see from the documentation there is no need to define a save point. All you need to do is create the dir “acf-json” in the theme root and ACF will automatically save to that directory there is no further code needed to make this work, but yes it does go on to explain how to create a custom save point if you do not want to use the default acf-json directory as the default.

Try it for yourself. Install a theme with ACF Pro and create the directory “acf-json” and create a custom field group. You will see that ACF does not need a save point defined and the group json will be added to the dir “acf-json”. Make sure your plugin in not installed first though.

Having your code defining the save point in your plugin now forces the theme developer to add their own save point code. I would think you would want to make this clear in your documentation that if you would like to use your plugin and use acf local json in your theme that you need define your save point.

• This reply was modified 5 years, 1 month ago by nickberens360.

@munirkamal It might be a good idea to add this issue to your plugin docs or better yet remove that piece of code from the plugins production code. I feel like 9 times out of ten theme developers are not defining their ACF save points. It seems a little heavy handed for a plugin to use that default save point. Just a thought.

@munirkamal yep that worked. Thanks!

I was able to reproduce using the twentynineteen theme.

Steps

– Install ACF PRO
– Create the acf-json dir in the theme root
– Install acfBlocks
– Create an acf group
– Look in plugins/acf-blocks/acf-json. You will see that the newly created field group is located in your plugins acf-json dir and not in the themes acf-json dir

Hi all, I am having the same issue. I am also using Desktop Server for my local environment. Any progress on this??

Hi Benjamin,

When I went to Theme Options and saved I received the following error:

Fatal error: require(): Failed opening required ‘/nas/content/live/wcha/wp-content/plugins/all-in-one-event-calendar/public/themes-ai1ec/vortex/less.sha1.map.php’ (include_path=’.:/usr/share/php:/usr/share/pear’) in /nas/content/live/lotusyoga/wp-content/plugins/all-in-one-event-calendar/lib/filesystem/misc.php on line 100

Im wondering if this something with this particular install and not on the plugin.