Support

Account

Register Login

Forum Replies Created

  • I’m seeing your post! Supposedly this was fixed in the latest version – have you tried updating?

  • is 8.5.2 live?

  • ok

  • Hi John – I appreciate your patience – my language is not precise and I want to make sure I understand.

    In step-2 above, in wordpress wpadmin, I open a page called Our Professionals. This uses a template called Professionals. In step 1, using ACF, I added a new field to all pages created with the template Professionals.

    On the Our Professionals page can now see this new field Job Title and I type “Partners” into the field. Press Publish.

    When I press Publish, the wordpess saving mechanism kicks in, and somehow ACF piggybacks on this, so the field Job Title and it’s content Partners is included and saved.

    I do NOT need to manually edit any PHP templates ( as in writing out PHP code to call the field ) .

    Correct?

  • Has this completely broken the plugin? Are there people who are still able to use the plugin despite this issue?

  • This is how I understand the process:

    1) I create a field using the plugin, and assign it to all posts (?) of a certain type ( template, page, etc )

    2) On that specified page, I now see the field, and can add content.

    3) I hit publish and now people can see the page

    Are you saying that for this to be visible to public, I have to edit the template code?

  • I’ve been told via support that it is being worked on. I don’t understand this at all, especially for a paid plugin – shouldn’t there be some clear discussion of the problem? an ETA on a fix?

    Are other people able to use this plugin? It seems like the one thing this plugin does ( add custom fields ) isn’t working.

  • nice!

  • heh

  • huh, maybe the embedded images are requiring moderation or something. Thanks for trying!


    @bartyfilm     do you have a plugin for rolling back the core install? I’m using WP Downgrade | Specific Core Version

    I’m assuming you have backups using updraft or something. If not, definitely get those now.

    Try rolling back to 4.9.10, see if it works there. If so, try upgrading to 5.0. What was the last version it was stable for you on?

    Here is a list of versions you can upgrade through until it breaks:
    https://wordpress.org/download/releases/

  • Sure! If that fails, here is the short version for other peeps:

    TLDR: go into ACF, assign your fields to POSTS or other non-custom page. Save. Confirm they are working. Then go back and reassign those rules where you want them. See if this fixes it. It’s working for me on wp 5.2.

  • What the heck. I just wrote a long post with a possible solution, and I’m not seeing it here.

  • @bartyfilm I found a partial solution. I think that ACF is not recognizing custom types of posts/pages ( I’m not sure what correct terms are ) .

    We use a type of post called Project.

    I toggled it to affect normal posts instead of Project. Viewed the “Post” and it was working. Then toggled it back to Project – and the custom fields are showing up now on the backend.

    Do you have custom post/template types?

    background:

    I originally rolled from 5.2.1 to 5.0 – and still experienced the problem. So I have been upgrading slowing, starting with it being stable on 4.8. I was surprised to find that this time, when I got to 5.0 it appeared to be working. At least, it was working on _Existing_ pages, I forgot to check creation of new items. My first thought was that it was necessary to do a major upgrade at a time ( 4.8 -4.9->5.0->5.1 )

    When I got to 5.1, I found existing pages were still working (!), and was excited my plan worked. However new pages, did not – they lacked the necessary custom forms.

    I went into ACF, and everything looked ok. So I tried assigning those fields to another type of post and it worked. When I toggled them back to “projects” now it works.

    I found this interesting – when I loaded up a project to review I saw this:

    There is an autosave of this post that is more recent than the version below.View the autosave

    When I compare the two I see that the “newer” version ( a draft that was saved during the upgrades ) lacks the custom fields.

    So my best guess is that ACF is not honoring the existing rules, and they need to be re-saved for them to “stick”.

    I’m running on 5.2 right now, and that’s good enough for the short term. I’ll mess with it more after the conference I’m supposed to be prepping for 🙂

    Have you found the most recent version of WP that yours works on correctly?

  • Thanks! For the time being I’ve rolled WP back to 5.0.4.

  • I am experiencing same issue as OP. This broke sometime after 5.0.4. Have any of you resolved this issue?

    I just upgraded from WP 4.8, plugin broke, and now I’ve been slowing upgrading to find where it breaks.

Viewing 15 posts - 1 through 15 (of 15 total)