Daniel Maier

@samuelaguilera yes, I forgot to mention that. We are indeed using our fields inside a flexible content field. That allows us to drag/drop these fields and reorganize how they are displayed.

I believe if you add another check using get_sub_field_object (but also keeping get_field_object) to find the text, text area and WYSIWYG fields that may do the trick.

Thanks again! ????

@samuelaguilera this is how I have to load my shortcode text field in my template:

$shortcode = get_sub_field(‘shortcode’);

Instead of:

$shortcode = get_field(‘shortcode’);

• This reply was modified 4 years, 3 months ago by Daniel Maier.

I looked at your code and I believe you also need to check using “get_sub_field_object” as well to cover the main fields and sub fields.

The shortcode text field I’m using is a sub field.

Hi @samuelaguilera,

I just tried the development version and I still got the cache for the page using ACF text field to embed the Gravity Forms:

cache-control: max-age=600, must-revalidate

I have captured a couple screenshots:

Field type: https://www.dropbox.com/s/fo382wm9hkqjmah/Fresh%20Gravity%20Forms%20-%20Field%20type.png?dl=0

Shortcode: https://www.dropbox.com/s/9ldeezhpdr6rnhf/Fresh%20Gravity%20Forms%20-%20Shortcode.png?dl=0

Thank you for working on this!

@mihaiimagely is there any way to know the ETA on this. It is really affecting our production this conflict.

I appreciate the effort.

Thanks.

Hi @samuelaguilera,

That would be an awesome addition if you decide to support it.
The fields we use are: Wysiwyg Editor, Text and Text Area.

Thank you.

Thank you that would help tremendously as it is interfering with productivity and affecting other plugins.
We would hate to have to leave NextGEN Gallery for another alternative.

I appreciate the assistance.

You will need a different plugin for that. Like Members for example. You can remove edit_others_post permission role or something like that.

That’s what I saw them too. Thanks @bueltge. I appreciate it.

@jessy86 what other plugin did you use?

@samuelaguilera thanks for letting me know about that. Since I didn’t know much about how the plugin worked I figured I would ask. I thought that was normal but wanted to double check. And yes, I was troubleshooting another Gravity Forms issue and decided to look into the logs from your plugin as well.

I appreciate getting back to me. Take care.

This has been fixed: https://github.com/markjaquith/page-links-to/issues/101

Issue has also been reported on GitHub: https://github.com/markjaquith/page-links-to/issues/101

I’m having the same issue.

Uncaught TypeError: Cannot read property 'tagName' of null –– new-tab.js?ver=3.3.1:1
at n (new-tab.js?ver=3.3.1:1)
at HTMLDocument.o (new-tab.js?ver=3.3.1:1)

• This reply was modified 4 years, 9 months ago by Daniel Maier.

Hi @mihaiimagely,

I’m not sure if NextGEN changed or Members changed but as I mentioned before, NextGEN even before would never “hold/memorize” the roles and permissions set in “other options”, every time I needed to make a change to the options I had to make sure I manually set the permissions to the appropriate roles every time or it would lose those settings.

As an alternative I can go to “Members” plugin and set it from there, each capability for each role, it is a bit more tedious since I have to edit each role. So if you can add to the feature request for them to review that section of your plugin that would be awesome!

Thanks!