Grant Palin

Replacing the create_function usage with an anonymous function (i.e. a closure) seems like an easy solution, however anonymous function usage would push the minimum PHP version requirement to at least 5.3. Speaking for my own use this would be fine, however as this plugin is widely used this update is not as simple as it seems.

• This reply was modified 6 years, 11 months ago by Grant Palin.
• This reply was modified 6 years, 11 months ago by Grant Palin.

Sure, I’ve done this myself. Custom types with custom fields through Pods, then some other custom fields through ACF. ACF does some things a bit differently, sometimes helpful, and it has the Repeater addon for which Pods currently has no equivalent.

To be honest, it was some months ago that I had tried it previously, so I can’t recall the details. However, it was setting up 2-way relations between all the types listed above – quite a web of connections. Getting near the end of setting them all up, WordPress balked badly, which at the time I assumed was something to do with all those connections, since that was the only change I had made.

I’ve recently given this setup another try, and it’s actually working well – far better than it did previously. Two-way connections, multiple selects, no trouble establishing or displaying the relationships. The issue I had previously might have been an issue with the then-current version of WP or Pods, or perhaps in how I did it. Doesn’t appear to be any problem now. Just though I’d inquire as to whether there were limitations in how many bidirectional connections could be used.

I’ve had the Markdown processor mess with my shortcodes too. Gets to be annoying sometimes. The author’s recommended workaround is to wrap the shortcode in a div element, like so:

<div>[caption id="attachment_22" align="alignright" width="300"]<a href="image-url"><img src="thumbnailurl" alt="Test-Caption" width="300" height="199" class="size-medium wp-image-22" /></a> Test-Caption[/caption]</div>

As a rule, Markdown will not do anything inside block elements. So this simple workaround should prevent the processor from mucking around with your caption shortcodes.

Strangely, the aforementioned error went away after I deleted the plugin and reinstalled from the repo. The default styling is back as well. Must have been some oddity with the current install.

Though on the backend, I now see a new message at the top, below the navbar:

Strict Standards: Declaration of PageNavi_Options_Page::validate() should be compatible with scbAdminPage::validate($new_data, $old_data) in C:\Users\grant\Projects\Websites\infectionNet\wp-content\plugins\wp-pagenavi\admin.php on line 156

I’m on a security kick lately, and have been taking steps to tighten up my WordPress site, so advice like this is welcome to see for making plugins work together. Thanks to the custom code section of the BPS settings, I’ve kept custom rules such as the 5G blacklist (https://perishablepress.com/5g-blacklist/), the Better WP Security rules, and some miscellaneous items (should probably review and prune those). So thanks for accommodating other plugins!

For some of the items in the list – scheduling regular backups, protecting login from brute force attack, and actively looking for changed files – I’m already using distinct plugins to handle those concerns. Yet these items remain as unresolved issues in the list. Perhaps provide a checkbox for these to indicate that they are handled separately?

These quibbles aside, I appreciate having all these potential issues reported in one place, along with recommended resolutions, so well done!

@joseph Bing can be given the precise filename of the sitemap file. I just submitted my site’s new sitemap (generated by WPSEO) and Bing requested the filename.

I used to use Subversion for my code, but switched to Mercurial and host my repos on Bitbucket. I’ve tried Git, and Mercurial just seems easier to use on Windows. Private repos are free on Bitbucket, and you get a handful of users for free on a team setup. Beyond five users in a team, pricing looks reasonable. With distributed systems it’s easy to work with a local repo to get the feel for it before committing to a host.