Status
Not open for further replies.

neounix

Customer
Hi Again!

We have a custom 404 error script process located at:

Code:
[html-document-root]/404.php

We have tried many configurations in the DBSEO settings, including:

Code:
[html-document-root]/404.php
[absolute-unix-path]/404.php
/404.php

.. but none of them work! Which format is correct?

Screen Shot 2013-12-11 at 5.40.55 AM.webp

Please note the HTTPD error message returned is:

Cannot access directly.
 
Last edited:
Httpd error log:

ip address - [10/dec/2013:16:44:46 -0600] "get /ffff/dfdf.php http/1.1" 404 242 "-" "mozilla/5.0 (macintosh; intel mac os x 10_9_0) applewebkit/537.36 (khtml, like gecko) chrome/31.0.1650.57 safari/537.36"
 
Yes, it is a HTTPD error being returned because DBSEO is not working property with the custom 404 setting.

If I turn off DBSEO it works perfectly fine, as it should and return the proper custom 404 page.
 
If you already have the custom 404 setup and is actively being used on your server, then using the second option "Send HTTP 404" should also use it.
 
OK. Let me test further tomorrow and post back.

It's 6 AM here and time to try to sleep. LOL

EDIT: My brain is dead from pulling an all nighter !m... I think its more-than-likely an error in the apache2 config file on our backup server.... I'll investigate further tomorrow.
 
Last edited:
I did discover an issue where if you attempted to include a custom vBulletin-powered file, it would display a blank page rather than the actual file.

However, that doesn't explain the issue you're seeing, so I'm still inclined to believe it's a server issue. I'll await your research findings :)
 
I'm pretty sure this is a server issue on our backup / test server; because we still have the issue with DBSEO is turned off; so I vote we move this to [NOT_A_BUG] and I'll revisit this again when we install DBSEO on our main server after testing is done.

Thanks!
 
/dbtech/dbseo/includes/class_core.php was hotfixed for this :)

Uploaded new file, was still having issues so I uploaded entire mod again in case fix was also contained somewhere else. Still not getting my custom error pages to show.

I have this in my root .htaccess

ErrorDocument 400 /error/400.php
ErrorDocument 401 /error/401.php
ErrorDocument 403 /error/403.php
ErrorDocument 404 /error/404.php
ErrorDocument 405 /error/405.php
ErrorDocument 410 /error/410.php
ErrorDocument 500 /error/500.php

All my error pages are vb custom pages and reside in root subdirectory /error and work everywhere currently except within DBSEO rewritten directories.
 
I'm not sure whether ErrorDocument is supposed to work with header() set errors - I updated your 404 handler setting in DBSEO to include the path to 404.php and it's now displaying correctly for me :)
 
I still see issues with errors.

For example with a 410 - Page Does Not Exist.

If someone types in a url or goes to a bad link within a DBSEO modified area all that comes up is a white page with "page not found".
If someone types in a url or goes to a bad link NOT within a DBSEO modified area my custom 410 error page gets displayed.

You can see this by just going to my site and modifying a bad url from /forum/xxxx to /forums/xxxx

------------------------------------------

Edit: Retesting now, may have just been a browser caching issue

------------------------------------------

Edit2: It does appear to be showing the 404 custom error page now. Thanks.
 
Last edited:
What the server is responding with a 410 error outside of DBSEO modified areas is getting a 404 within DBSEO modified areas.

Currently...
If you take any random url on my site that does not exist a 410 error will display - saying this page does not exist.
If you take any random url - within a DBSEO modified directory - on my site that does not exist a 404 error will display.
 
That's highly strange that your server displays 410. In either case, the 404.php file seems to be working fine for you now :)
 
So, when we configure for a custom php error processing file... we use the relative path to document root, I assume?

For example, if the custom 404 is in the HTML document root and is called 404.php... then we put

404.php?

or

/404.php

or

/document/root/404.php

?
 
Status
Not open for further replies.

Similar threads

Legacy DragonByte SEO

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