Aubrey Portwood

Works for me in 5.2.1?

1. None
2. No
3. Not sure, but this doesn’t use cookies as far as I know

– Yes
– Yes
– Yes

There is, but that would require custom development to get those to show.

Right now there’s no official support for any page builders. I do want to update Noteup for Gutenberg compatibility, but that’s about it.

This likely is because of some incompatibilities with CMB2. Thanks for your feedback, and as soon as I have time to, I will likely update it at some point.

I’ve filed https://github.com/aubreypwd/wp-noteup/issues/73 as a reminder to see if I can get these things worked out.

There was an update 1.2.1 pushed out the other day that should fix this issue.

@jdembowski If you view this page https://www.ads-software.com/support/topic/call-to-a-member-function-add_help_tab-on-null-in-wp-adminnetwork/ you will see that @mateuszgbiorczyk hasn’t requested access to anything on this post.

@mateuszgbiorczyk I have attached a patch above with a fix.

@jdembowski Did you get the right post? ˉ\_(ツ)_/ˉ

When I look at: All Post or Pages – it is not showing up there. When I look at an individual post/page, I can see it there.

This is how it’s intended to work, only on the post/page edit screens.

An icon? Got an example?

This is intentional. Due to a bug with CMB2, we can’t allow that box to be moved around anymore. As soon as you do, the content will be lost in the editor. I’d love to fix this at some point in the future, but to avoid data loss and UI breaking, I had to do it this way.

• This reply was modified 8 years ago by Aubrey Portwood.

Err, after some review of plugin guidelines, it appears this is not possible:

14. Frequent commits to a plugin should be avoided.

The SVN repository is a release repository, not a development one. All commits will trigger a regeneration of the zip files associated with the plugin, so only code that is ready for deployment (be that a stable release, beta, or RC) should be pushed to SVN. Including a descriptive and informative message with each commit is strongly recommended. Frequent ‘trash’ commit messages like ‘update’ or ‘cleanup’ makes it hard for others to follow changes. Commits that only tweak minor aspects of the plugin (including the readme) cause undue strain on the system and can be seen as gaming Recently Updated lists.

So this will not be the case going forward.

I can’t remember to be honest, but I’ve filed a ticket https://plugins.trac.www.ads-software.com/ticket/2588 to look into it.

If you want to contribute, the Github repo is here.

https://github.com/aubreypwd/gravityforms-firstdata

If you fork, just let me know where the new fork is. We can work together to ensure you can push an updated version to the SVN repo here too.

I’m totally okay with it, as I will not (and do not) have the time to work on this plugin anymore.

I have Gitter on pretty much all the time, if you want to chat more hit me up there https://gitter.im/aubreypwd/gravityforms-firstdata

Since this is a feature request, I’ve created https://github.com/aubreypwd/easy-photo-album/issues/10 to track it.