Resource icon

Thread SEO changes [Paid] 1.1.4

No permission to buy ($35.00)
It seems the validation stops (fails) when it hits redirects that are not resolved. i.e. because there are patterns that are not fixed, it will stop checking the rest of the URLs. So its needed to keep starting a new validation after it stops. Naturally, the % of unresolved redirects will increase and validation becomes harder as you go. Upside of this is that you will end up with a list of redirect url patterns that still need fixing.
 
@Xon
Are you considering to add similar rewrites for XFMG?
What are your thoughts about the /unread link?
 
This add-on should remove the /unread link for guests, but for normal users it keeps it around.

As for XFMG I haven't had any requests for support for that add-on
 
If I understand correctly, for example, the prefixes for guests and robots are no longer clickable?

If that's the case, then something's wrong on my end after the installation :D
 
It depends on what you mean by "clickable", as there is a couple of cases where XF implements that sort of thing.
 
The link looks the same with or without the add-on.

Code:
<a href="/bereich/event-zone.558/?prefix_id[0]=96" class="labelLink" data-xf-init="tooltip" title="Zu den Filtern hinzufügen"  rel="nofollow"><span class="label label--green" dir="auto">News</span></a>
and not only visible to guests but also clickable, which shouldn't be the case if I understand the system correctly.
 
@Xon I have a node with lots of topics (3000+).
With this add-on enabled, it takes 5+ seconds to open this node. With this add-on disabled, it takes a second.
Is there any way to improve this?
 
With this add-on enabled, it takes 5+ seconds to open this node. With this add-on disabled, it takes a second.
This is likely an add-on compatibility issue of some sort.

I'ld need to see the sql query log for the effected page, can you open a ticket so I can get that information to debug?
 
This appears to be an unexpected performance regression due to fetching the last post. I may need to investigate how to remove that join.

For now can you try installing this add-on?
Then set the "Better Thread List Page Threshold" option to 0?

This will restructure the thread list query to fetch less data from disk at once.
 
A setting to get 410 status code on deleted threads would be very helpful. Could be global or per node. Or per thread and apply it with criteria or batch process threads.

 
I have a small Not Found On Unviewable add-on which makes it return a 404 instead of a 403; but the 410 is pile of policy choices which is harder to work out.

It covers a extending a few other add-ons, not just threads.
 
Back
Top Bottom