Question Fix 500 error

Status
Not open for further replies.
It is not going to fix any URLs that were posted on your site, no.

Finally pinpointed where I think the problem is coming from.


This setting: "(Pro) Custom Thread URL"
Using [forum_title] or [thread_title] -- any way, shape, or form causes only some of the threads not to work. When I turn off Custom path the options that have [forum_title] or [thread_title] still does not work. I have since removed these options. And it appears all the threads and forums are working fine with the removal of "[forum_title] or [thread_title]."

I'm hoping know what we broke to cause these options to no longer work. lol
 
Sounds like adding those options causes a conflict with other URL formats then, try adding unique text such as "thread-" etc to each of the settings.
 
Sounds like adding those options causes a conflict with other URL formats then, try adding unique text such as "thread-" etc to each of the settings.

I think all of the options that need it, already have "Thread-id" in them. Do you have any other options or maybe its something I'm missing?
 
Sorry, I should have been more clear. I mean if you have a thread URL format as [thread_id]-[thread_title] and a forum URL format as [forum_id]-[forum_title] it is impossible for the mod to distinguish between the two.

You need to make them f.ex. thread-[thread_id]-[thread_title] and a forum URL format as forum-[forum_id]-[forum_title] so that the mod can tell them apart.
 
Sorry, I should have been more clear. I mean if you have a thread URL format as [thread_id]-[thread_title] and a forum URL format as [forum_id]-[forum_title] it is impossible for the mod to distinguish between the two.

You need to make them f.ex. thread-[thread_id]-[thread_title] and a forum URL format as forum-[forum_id]-[forum_title] so that the mod can tell them apart.

Alright. So I took the "[forum_id]-[forum_title]" out of literally all of the options. Some of the threads still redirect to the index page and some don't.
 
I'm not sure how taking out stuff from the options would fix what I mentioned in my previous post?
 
I'm not sure how taking out stuff from the options would fix what I mentioned in my previous post?

Maybe I didn't understand what you're saying. I thought you said with the 2 options in there, it can't tell the difference. So I went through all the settings and removed the "[forum_id]-[forum_title]" from all the options. Therefore it wouldn't conflict with [thread_id]-[thread_title]. At least this was my understanding.
 
The conflict issue may be better explained by this:

For instance, let's say you have a forum format like so:
[forum_title]-[forum_id]/

And a thread format like so:
[thread_title]/

As far as DBSEO is concerned, the two URLs look like so:
<any character or symbol>-<a number>
<any character or symbol>

Now let's assume someone posts a thread title like so:
New Release: DBSEO version 2

The rewritten URL for that thread would, without the -a suffix, be:
new-release-dbseo-2

Notice how this matches the <any character or symbol>-<a number> rule for forum URLs? In other words, if forum URLs are given a higher "priority" than thread URLs, the rewritten URL would be resolved as if it was a forum, and when visiting that thread you would see forum ID 2 (or an error message, if that forum ID does not exist or is inaccessible).

However, with the rewritten URL including the -a suffix, the URL for that thread would be:
new-release-dbseo-2-a

Notice how it no longer matches the <any character or symbol>-<a number> rule for forum URLs? There is now a character after the number, which means it can't be a forum URL.


This is a very simplified example, but it demonstrates why it's vitally important to make sure that URL formats can be resolved as accurately as possible.


That's a canned response to whenever we get someone asking for why there's an -a in certain titles, but the same principle applies - the title and ID variables still resolve the same way in this case.
 
The conflict issue may be better explained by this:

For instance, let's say you have a forum format like so:
[forum_title]-[forum_id]/

And a thread format like so:
[thread_title]/

As far as DBSEO is concerned, the two URLs look like so:
<any character or symbol>-<a number>
<any character or symbol>

Now let's assume someone posts a thread title like so:
New Release: DBSEO version 2

The rewritten URL for that thread would, without the -a suffix, be:
new-release-dbseo-2

Notice how this matches the <any character or symbol>-<a number> rule for forum URLs? In other words, if forum URLs are given a higher "priority" than thread URLs, the rewritten URL would be resolved as if it was a forum, and when visiting that thread you would see forum ID 2 (or an error message, if that forum ID does not exist or is inaccessible).

However, with the rewritten URL including the -a suffix, the URL for that thread would be:
new-release-dbseo-2-a

Notice how it no longer matches the <any character or symbol>-<a number> rule for forum URLs? There is now a character after the number, which means it can't be a forum URL.


This is a very simplified example, but it demonstrates why it's vitally important to make sure that URL formats can be resolved as accurately as possible.


That's a canned response to whenever we get someone asking for why there's an -a in certain titles, but the same principle applies - the title and ID variables still resolve the same way in this case.

Maybe I don't really understand. We even restored the settings from a few months ago when everything worked fine -- besides a very few minor problems. The format is still the same. So why would 1 day out of the blue it would just stop working. Also, I don't know if this helps but it seems like all of the threads that are redirecting to the Index.php have the same Thread-Id and Thread-Title.

FeverClan | Gaming Community

Everything that we have problems with seems to have (57729-fever-cs:go.html) on them -- instead of the actual thread information.


Also, just noticed another problem where this thread has the wrong {thread]-Title
Pending: Infinity's Application
 
The redirect might have something to do with the : character, as that's not usually valid in URLs. Can you please try adding it to the character filter?
 
The redirect might have something to do with the : character, as that's not usually valid in URLs. Can you please try adding it to the character filter?

That is what I was thinking. So I had turned on "Remove Non-Latin Characters" thinking that might take care of the problem. I take it that I need to add it specifically to the custom character. I just don't know what you replace ":" with.

"This setting lets you filter custom characters from the SEO URLs.

Examples:
Č => c
ş => s"


A side note, should I just remove the plugin altogether and reinstall?
 
Just do

: =>

You don't have to add anything to the replacement side :)

You'll never believe this...So that didn't fix anything. lol


- So I created a fresh backup -- then deleted the plugin -- installed it again -- Restored with same fresh backup -- Everything seems to work again. So I take it wasn't a configuration issue.
 
Hello feverc5,

This ticket has now been closed with the status Answered.

We hope your issue or question has been addressed to your satisfaction. If not, please feel free to re-open it by clicking this link.

If you have any further issues or questions, please feel free to start a new support ticket via the button at the top of every page.

Thank you!
 
Status
Not open for further replies.

Legacy DragonByte SEO

vBulletin 3.8.x vBulletin 4.x.x
Seller
DragonByte Technologies
Release date
Last update
Total downloads
7,169
Customer rating
5.00 star(s) 1 ratings
Back
Top