Question Paths rewrite on activation

[Zuker]

Hi, i'm migrating from vbs. to dbseo, and after activation product (vbseo it's off) all my paths are wrong

GAM!NGA - Foros

check css, for i.e., it should be in /common and it says it's in /foros/common

htaccess

RewriteEngine On


RewriteBase /foros/

# If you are having problem with "None Could Be Negotiated" errors in Apache, uncomment this to turn off MultiViews
# Options -MultiViews

RewriteCond %{REQUEST_URI} !(admincp/|dbseocp/|modcp/|cron|mobiquo|forumrunner|api\.php|reviewpost/|classifieds/|photopost/)
RewriteRule ^((archive/)?(.*\.php(/.*)?))$ dbseo.php [L,QSA]

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !/(admincp|dbseocp|modcp|clientscript|cpstyles|images|reviewpost|classifieds|photopost)/
RewriteRule ^(.+)$ dbseo.php [L,QSA]

thanks in advance

 

[Zuker]

UPDATE

I've changed the URL of the site to gaminga.com, and the component to foros, and external css it's almost loading fine now, but all the images and css from bulletin aren't, so i think or i'm missing a configuration or something it's buggy

Thanks in advance

ps: I've disabled dbseo since i need the site to be working

 

[Fillip H.]

Could you please create and PM me with a temporary FTP and AdminCP account?

For security reasons, we recommend you create a new FTP account only for DBTech support, then disable or delete it after we have both confirmed the issue has been solved and there are no further issues.

The same applies to AdminCP accounts; they should ideally be temporary accounts created for us only. If we have created an account on your site already, you can optionally boost that account to Administrator and then de-admin this account once the issue has been solved.

If you use a .htaccess password protection for your AdminCP directory, it is recommended that you create a new authorised user for DBTech and remove this user once the issue has been solved.

Please test any temporary accounts you create to ensure that the FTP account has access to the forum files, and that the AdminCP account can access the administrative controls for the product we are assisting you with.

Ensuring this is all in order before submitting the information will significantly speed up the process of assisting you. We will alert you via PM if there's any issues with the login information you have provided.

When sending the PM, for your security you should also un-tick the "Save a copy in my Sent Items folder" checkbox. When the access details have been received, we will delete the PM from our inbox. Ensuring you have not kept a copy of the PM reduces the risk of security breaches.

Thank you for helping us debug our products and allowing us to assist you, we appreciate it

 

[Zuker]

Data Sent! TY

 

[Zuker]

Any updates? TY

 

[Fillip H.]

I will post back when I have updates for you, bumping your thread will not move your issue up the queue any faster

 

[Fillip H.]

Update: This is a bug in your custom skin. This is evidenced by the fact that your forum works fine in the default style.

Due to the extensive customisations to the skin in question, I will be unable to assist you with this issue. It's simply not feasible for me to revert each template and detect which specific customisation is causing this issue. Sorry

 

[Zuker]

Using vbseo i've got no issues ....

And customizations are very simple, and i use full paths starting with "/"... weird...

There it's something in the mod that adds "/foros/" to url's in templates

with mod disabled

<link rel="stylesheet" type="text/css" href="/common/style.php"/>

with mod enabled

<link rel="stylesheet" type="text/css" href="/foros/common/style.php"/>

???

Thanks for your time

 

[Fillip H.]

<link rel="stylesheet" type="text/css" href="/common/style.php"/>

with mod enabled

<link rel="stylesheet" type="text/css" href="/foros/common/style.php"/>

This is your problem. This is literally the opposite of "full paths".

Change the URLs to

<link rel="stylesheet" type="text/css" href="{vb:raw bburl}/common/style.php"/>

 

[Zuker]

Templates are imported from php files from the external website using something like this

// head header
ob_start();
include('/var/www/gaminga.com/public_html/common/header_head.php');
$include_header_head = ob_get_contents();
ob_end_clean();
vB_Template:reRegister('headinclude',array('include_header_head' => $include_header_head));

For full paths i mean that starts with /

 

[Fillip H.]

You need to fix the URLs so they are using the full HTTP URL, not starting with /. This is a bug in your code for your custom skin.

 

[Zuker]

There its no real need of doing that, the proof its that with this mod disabled, site its working fine. Even with vbseo enabled and all other mods site its working fine

 

[Zuker]

Just for testing, i've added the full path and the problem it's still there

 

[Fillip H.]

If this is a problem with this modification, can you please explain to me why the default skin, and literally every other skin every other user has installed, works correctly? Can you please explain to me why it's only your skin, and only with your "WP to vB Skin Bridge" code the problem manifests itself?

If you are writing code that's actively designed to not follow the vBulletin URL standards (i.e. using / at the start of your URLs, rather than using the Forum URL or no / at the start), vBulletin and DragonByte SEO cannot be held responsible for what doesn't work on your forum.

 

[Zuker]

Ok, so i bought something that doesnt works... Great support here. I'll ask paypal for a refund since this it isnt working and i will continue using vbseo that works on my site.

Can you explain me why vbseo works fine and dbseo not?

 

[Zuker]

And i already told you that forum <head> code its included with full url support and it isnt working anyway

 

[Fillip H.]

I am unable to assist further as the FTP account you have created for me does not have access to the /common/style.php file you referred to in your previous post.

If you would like me to attempt to fix your code so that it's compliant with the vBulletin coding standard, I will need full access to it and any other file that's being included in your vB style.

 

[Zuker]

Nevermind, i'll find a way by editing all the whole site.

TY