Jeff Starr

Hi @foreclosurepedia, just wanted to follow up with this. It’s been a while with no reply, so I hope the issue is resolved? Or if there is anything I can do to help, please let me know. Thank you.

Shortcodes are a standard feature of WordPress core. Many thousands of plugins use them, and also millions of websites. Is there some specific reason why you would think that shortcodes should not be used? Or why a plugin that makes use of shortcodes would suggest deprecation?

For the deprecated message re: “Passing null to parameter”, thank you for reporting, it will be fixed if possible in the next plugin update.

Glad to help.

Actually installing USP is the same as installing any other WP plugin. Here is a guide that explains better than I would be able to do here:

https://ww.wp.xz.cn/documentation/article/manage-plugins/

Once you’re familiar with how to install a plugin, go ahead and install User Submitted Posts. That’s pretty much it. Then to use the plugin, there are a couple of first things that users typically like to do:

• Display the post-submission form by adding the shortcode [user-submitted-posts] to any WP Post or Page
• And/or visit the plugin settings page to customize options, etc.

I hope this helps, it’s basically an overview of the plugin documentation. Let me know if I can provide any further information.

Thanks, I have tested each of the following strings against the free version of BBQ:

/wp-admin/admin.php?page=CiviCRM&q=civicrm%2Fcontact%2Fview%2Fcase&action=view&reset=1&id=2

/wp-admin/admin-ajax.php

/civicrm/contact/view?reset=1&cid=XX&selectedChild=activity

action=civicrm

None of the above were blocked on default WordPress.

So I am guessing either that there are other POST/REQUEST variables being sent via Ajax or some other mechanism and that is what is causing the false positive. OR, it could be that some other plugin or theme is involved somehow.

Thanks for the information, I will see if there is any way to resolve this issue on this side of things. Feel free to post again with any further information, etc. Glad to help anytime.

I did look into supporting removal of the extra images added by every plugin and theme, but was not able to find a clean technique. There are too many plugins and themes that add their own image sizes, it would be virtually impossible to support/disable them all.

Best advice for removing any non-WP generated images is to add a snippet of custom code. I wrote a guide that explains various ways of doing so. I hope it helps, let me know if I can provide any further information. Thank you

Sure if you let me know the steps or requirements, I will try to implement. Thank you.

Hi gohskungfu, I hope you got this sorted. It’s been a while with no reply so gonna go ahead and mark this thread as resolved to help keep the forum organized. Feel free to post again with any further questions or feedback, I am glad to help anytime. Thank you.