How to: Fix front-end issue

  • If you want to fix the plugin to work on the front-end you will have to rename the
    /wp-content/plugins/calculated-fields-for-acf/admin/assets/calculated-fields-for-acf.js to ml/wp-content/plugins/calculated-fields-for-acf/admin/assets/calculated-fields-for-acf.min.js

    The plugin wasn’t working on the front-end because the calculated-fields-for-acf.min.js wasn’t load because it doesn’t exist.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor nick6352683

    (@nick6352683)

    Thanks, I’ll verify your solution tomorrow and report back here…

    Plugin Contributor nick6352683

    (@nick6352683)

    Sorry for the delay, I can now confirm that renaming that file fixes the issue. I will wait a few days for the actual developers to update the plugin, as I have no access to do so, and if nothing is done, I will make sure with the moderators that I will not be breaking some rules of theirs, and create a sticky post in the support pages and put an external link for the fixed update of the plugin. That’s all I can do for now…

    But really, thanks to you @elyfornoville , I can update and use the latest version of the plugin finally now… Thanks a million !!!

    Plugin Contributor nick6352683

    (@nick6352683)

    I think I spoke too soon. The fix by renaming that js file works for regular number fields without any issues, but it does not work with calculations involving Repeater Sub Fields. With the subfields the calculations are correctly done, and displayed in the backend, but are not stored on the front end since the calculated fields are unabled to be stored in the database.

    Unfortunately, or fortunately reverting back to version 1.3 everything works fine again….

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘How to: Fix front-end issue’ is closed to new replies.