Testing DBSEO and running into a couple of issues

Status
Not open for further replies.

capflam

Customer
Hi,

I am finally testing DBSEO and have a couple of issues. It's on a test intall so this isn't critical at this point:

1. After intalling DBSEO, my header got messed up for some reason. I am using a custom header, but that surprised as I can't figure out what DBSEO has to do with it.

2. I didn't find the VBSEO import settings and I don't find where I could actually set those settings I had. Is there a way to check this.
Specifically I had a maximum number of words in the thread URLs and I want to know if this is going to be supported.
I'm happy to share my XML if it helps.

3. I see that some characters such as "à" are not taken into account and replaced automatically like in VBSEO. How can I manage this? Just use the character replacement option?

4. I didn't notice any load / speed improvement VS VBSEO. Actually I think that all is a bit slower. That's not normal right?

Thanks
 
1. Could you please provide more information? "Messed up" isn't very descriptive ;)

2. vBSEO import is a Pro-only feature, I can confirm the max keywords is indeed a feature.

3. There is a setting for this, Non-Latin Characters.

4. If you have APC, XCache or Memcache installed on your server, you can configure vBulletin's config.php file to take advantage of it which will carry over to DBSEO.
 
Hi,

Thanks for taking the time to answer.

1. Yep :). I meant that there was a background div that doesn't display any longer. It also now displays a floating div (a ribbon) below the top navigation.
This is a custom header so it's not the stock vbulletin header but I wonder how this could happen.

2. 3. Ok thank you. So all seems to match my customization then. I just need to figure out which characters are not in DBSEO but were in VBSEO.

4. Does it work with eAccelerator?

5. Is there a promo code these days? :)

Thanks
 
1. You'd best contact your skin developer for that, if it's anything like the BluePearl skins they have used an incorrect coding technique to achieve their goal.

4. Yeah, but eAccelerator is not as effective nor as compatible as XCache.

5. Not at the moment, no, sorry :(
 
As this ticket has received no further replies, I'll close it.

If you have any further questions or issues, please feel free to create a new ticket. Thanks!
 
Status
Not open for further replies.
Back
Top