fawp

Ok thanks @amimulihsanmahdi

Ok, thanks Rogier.

@rogierlankhorst could it have to do with the fact that I did not update via the ‘Update’ button provided by your plugin but performed a ‘manual’ update?

Manual updates are necessary for environments where version control testing is important.

@rogierlankhorst in answer to your question: I just checked

1. I have reverted to a snapshot prior to installing Really Simple SSL
2. I have upgraded BP from 8.0.0 to 9.2.0
3. I have then installed Really Simple SSL
4. Really Simple SSL no longer reports the vulnerability in question, as expected

• This reply was modified 1 year, 8 months ago by Jan Dembowski.
• This reply was modified 1 year, 8 months ago by fawp.

Hi @rogierlankhorst – I’m happy to provide it here.

It’s BuddyPress v. 8.0.0, upgraded to v. 9.2.0.

Does that mean that your plugin does not need a ‘rescan’ button, because it automatically scans again?

Thanks.

• This reply was modified 1 year, 8 months ago by fawp.

@andrewza Hi Andrew, thanks.

From WP-CLI dev team:

was already fixed in the latest code which will be included with release v2.5.0.

You can already test the fix with the WP-CLI nightly version, which you can use via wp cli update –nightly.

Hi bcworkz, my pleasure.

Sure, happy to submit notes in there, I will do so now.

Thanks for the suggestions about require_once() and HTML, I’ll probably go for the latter!

Excellent! I’ve just tried get_pages() and it works. Thank you so much for taking the time to post this, bcworkz! ??

I have just tested it on 5.3.2. The plugin as it is works, however, when logged on as a user with Editor privileges or lower, it will throw out a notice such as

Notice: WP_User->id was called with an argument that is deprecated since version 2.1.0! Use WP_User->ID instead. in /var/www/automenu.local/wp-includes/functions.php on line 4865

If you are comfortable in editing code, locating manage_your_posts_only.php in your plugins folder and changing the line

$wp_query->set( 'author', $current_user->id );

into

$wp_query->set( 'author', $current_user->ID );

makes the error disappear.

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

Great, thank you very much for your help bcworkz!

Many thanks for your answer and apologies about the breach of netiquette.

It may be that I misunderstood my request to be similar to that in the topic https://www.ads-software.com/support/topic/hierarchy-post-type-post-table-custom-sort/ – I do see in that topic that a reference is made to “$hierarchical_display is set for any hierarchical post type and it essentially forces children to be listed under their parent”. I understand that property belongs to the WP_Posts_List_Table class.

Does that mean that through WP_Posts_List_Table hierarchical CPTs are shown hierarchically, but attempting this via a WP_Query won’t work because of what bcworkz mentioned?

Thanks again
fawp

Marking as resolved.

@sterndata

Ok, thank you Steve, appreciate it.

Yes, it was that link. Thanks for fixing!