Sunfire
Forum Replies Created
-
Forum: Plugins
In reply to: [Contextual Related Posts] Bulk Edit disable on postsTurns out using the shortcode may work ok…. It changes the client’s current posting workflow yet this might be manageable. And with such a large site already, it will necessitate some additional work to revisit posts and add the shortcodes individually after I turn off “automatically add” in the general settings….
In this particular instance, I see that using the shortcode with a
limit=#where the # is the same as the number of manually selected related posts seems to do the trick.While it may create some rework for this client, I’m noting it here for others who may find this topic later.
To bypass the base settings, use something like
[crp limit=4].Thanks again for the reply, Ajay. I appreciate your honesty and I respect that new features would only be added to Pro.
Forum: Plugins
In reply to: [Contextual Related Posts] Bulk Edit disable on postsThanks for the reply Ajay. I will look into the options and see what will be best for my client’s current workflow.
Forum: Plugins
In reply to: [Contextual Related Posts] Error after update to 4.2.0Ah, now I remember…. We sometimes manually select related posts, but only one or two. Having a value in “number of posts” meant more posts would be included beyond the manually selected ones, which was not ideal.
Is there a way to ensure that, if we manually select related posts but the number of manually selected is fewer than in the settings, additional “related” posts are not added to the list?
Forum: Plugins
In reply to: [Contextual Related Posts] Error after update to 4.2.0I added a value in that setting (still on version 4.2.0) and that seemed to do the trick.
I forgot that I am not able to upload plugins manually for security reasons, so I couldn’t test the beta.
Thanks for the quick reply. Looks like we’re back in business on my client’s site.
Forum: Plugins
In reply to: [Contextual Related Posts] Error after update to 4.2.0I believe previously, if left empty, it would default to 6, but I could be mistaken. I will be sure to set a value in there just to be sure.
Forum: Plugins
In reply to: [Contextual Related Posts] Error after update to 4.2.0We are on PHP version 8.3.3 and left the number of posts setting empty (this used to default to 6, I believe, and that amount was fine).
I’ll see about testing that fix and report back.
Forum: Plugins
In reply to: [WP Sitemap Page] Sort by TitleThank you for this @dshakya – the reverse order of the results on my CPTs was about to drive me crazy.
For those willing to update the plugin code themselves until the original developer corrects this, I’m noting line numbers here for you. All changes are in the file
wp-sitemap-page.php– bold here indicates the additions per the previous suggestion.Line 593-594:
if ( !empty($cpt) ) {
return wsp_return_content_type_cpt_items( $is_title_displayed, $display_nofollow, $cpt, $only_cpt, $wsp_exclude_pages, $sort, $order );
}Line 980:
function wsp_return_content_type_cpt_items( $is_title_displayed=true, $display_nofollow=false, $cpt='', $post_type='', $wsp_exclude_pages='', $sort=null, $order=null ) {Starting on line 999:
// change the sort order
if ($sort!==null) {
$args['orderby'] = $sort;
$args['order'] = $order;
}Once I made all three of these changes and re-uploaded the file to my server, the shortcode used of
order="ASC"worked as intended.Looking over the code and logic, this may not be totally correct (I think the conditional on line 1000 should be
$sort!==null || $order!==nullor maybe separate conditionals…) but I am hoping by us posting these necessary changes, the plugin developer might see this thread, perfect the logic and code, and then release an update including these corrections in the near future.Thanks Danny! Sure thing, lemme see…..
So I installed it on my client’s site (less than 2 months worth of low traffic, so I figured it’d be okay)… There was a brief “critical error” that came up in the activation process, but reloading the site cleared it up and I am not seeing any other errors yet.
Here’s a look at the Top 20 pages listing now (showing paths instead of page titles) –
Seems to have handled the existing data okay…
I’ll have to poke at it when not logged in to see if I can get the Archive page (
/audit-firm/) to show up on this list…Thanks for sharing – let me know if you have anything else I should be watching for with this beta version…
Thanks for the explanation Danny. That does make sense, and I appreciate your attention to space-saving by using the post IDs.
Knowing this, I will inform my client… while also considering how I’d like to adjust our setup to be able to track visits to the main directory page. If I can wrangle blocks and the sidebar, maybe I’ll make an actual page instead of relying on the default-generated archive….
Thank you for the reply, however it doesn’t make sense that you would mark this topic “resolved” if you haven’t yet released a new version of the plugin. I’m reopening the thread so other users are not confused.
The WordPress plugin repository still shows this plugin as last updated 2 years ago.
Please release a freshly tested version of the plugin before marking this topic as “resolved.”
Thanks for the follow-up Peter. I looked at the logs again today – at one point the same IP had 30 different blocks listed in Wordfence with the same timestamp.
Since we have it so all the traffic should be going through CF, I went back there to check settings and verify things like rate limiting and Bot mitigation were in place and functioning. They are configured as I would expect, so I may just need to dig deeper and refine it.
It’s helpful to know that these multiple blocks are functioning as intended (slight delay) and not broken. Thanks.
And yes, for now I am just letting the duplicate entries expire and, adding a Permanent block on the entry that has recorded multiple hits, especially if they continued to hit more than 48 hours later (hence the 5 day lockout). Although these permanent blocks on specific IPs doesn’t seem to matter as the bots or attackers are rotating IPs regularly… it’s still helpful in my monitoring process.
As I mentioned, yes, my Rate Limiting rules are a bit strict. To answer your specifics, they are set to 240, 120, and 60, respectively. And yes, I implemented a 5 day block.
I do understand that Wordfence is only dealing with the traffic that actually makes it to our website. We are using Cloudflare and have hardened our server to only accept traffic coming from CF IPs.
What I’m asking is, how can the same IP have a dozen different blocks at the same timestamp? Why not just have a single block with a high incidence count?
Forum: Plugins
In reply to: [Simple Staff List] New staff not showing on front endWe thought it was cache at first, but it has now been 2 weeks since the changes were made and they still aren’t showing for logged-out users. Any caches along the way should have cleared by now.