Status
Not open for further replies.

janslu

Customer
I have installed dbseo on my test forum @ 401 Authorization Required
1. Installation was smooth but I think the documentation should have a step by step upgrade from vbseo walkthrough (I didn't know when to turn off vbseo for example).
2. Rules - my custom rules were not transferred to dbseo correctly. I will be happy to provide them as an xml
3. Custom Character Filter - custom accented characters replacement rules were transferred to a proper field in the dbseocp but don't work. I am using a table to convert for example ą to a, ę to e, ć to c etc. I have used the following in Vbseo:
'ą' => 'a'
'ć' => 'c'
'ę' => 'e'
I have tried different versions (with utf8 and without, with quotes and without, using enities instead etc) and I've always got some wrong variants including dashes inside. For example Kręcimy title becomes kr-e-cimy instead of krecimy I get using vbseo.
 
1. We'll aim for getting a decent set of documentation written up for the Gold release, if not then hopefully soon after that :)

2. Sure, if you could attach your vBSEO config XML file to this thread and give me specific information as to what exactly didn't transfer correctly so I don't have to guess, I'll definitely look at it :)

3. Am I to understand that the only actual issue is the insertion of the - around the replacement character? Let me know the exact details so I know what to test :)
 
1. I thought so ;-)

2. & 3. It's not that easy. Seems like a problem with string translation. My forum uses utf-8, but when I turned the utf-8 option on in dbseocp it got even worse. Default settings after importing vbseo settings give me the following example urls:

Code:
Threads:

dbseo: http://test.babyboom.pl/forum/f64/spea-nione-zaciae-a-one-staraczki-od-stycznia-2012-a-58243/
vbseo: http://test.babyboom.pl/forum/przyszle-mamy-f64/spelnione-zaciazone-staraczki-od-stycznia-2012-a-58243/


dbseo: http://test.babyboom.pl/forum/f64/przysza-e-mamua-ki-z-wae-tku-o-iui-62794/
vbseo: http://test.babyboom.pl/forum/przyszle-mamy-f64/przyszle-mamuski-z-watku-o-iui-62794/


dbseo: http://test.babyboom.pl/forum/f64/ciae-a-a-w-uk-proa-ba-o-pomoc-w-badaniach-64529/
vbseo: http://test.babyboom.pl/forum/przyszle-mamy-f64/ciaza-w-uk-prosba-o-pomoc-w-badaniach-64529/


======================

Latest posts:

dbseo: http://test.babyboom.pl/forum/f64/58243-spea-nione-zaciae-a-one-staraczki-od-stycznia-2012-a-post9950814.html#post9950814
vbseo: http://test.babyboom.pl/forum/przyszle-mamy-f64/spelnione-zaciazone-staraczki-od-stycznia-2012-a-58243/index79.html#post9950814

dbseo: http://test.babyboom.pl/forum/f64/62794-przysza-e-mamua-ki-z-wae-tku-o-iui-post9950470.html#post9950470
vbseo: http://test.babyboom.pl/forum/przyszle-mamy-f64/przyszle-mamuski-z-watku-o-iui-62794/index276.html#post9950470

======

Forum rules didn't transfer at all,
Thread rules work fine, except for the character conversions,
Paging didn't transfer

I will test more tomorrow.



These rules were decided on before vbseo set the templates, it's not that I HAVE to use them. One of the most promising features of dbseo is the ability to actually change some of them to a new, simpler set.
 

Attachments

  • vbseo_urls-2.xml
    16.9 KB · Views: 1
Last edited:
Hey,

I've actually made a fix to the importer, can you please re-download the latest version and re-upload /dbtech/dbseo/includes/vbseolookup.php & /dbtech/dbseo/actions/admin/vbseoimport.php, then re-run the importer?

I've checked your XML file, and it is supported by the importer :)

Once you've done so, and confirmed that the URL formats are being imported correctly, can you then please paste the following pieces of information:
1. The vBSEO version of a thread URL that contains UTF-8 characters
2. The DBSEO version of a thread URL that contains UTF-8 characters
3. The character set used by your language in Language Manager -> Edit Settings
4. The character set used by your database (can be found via phpMyAdmin

If I'm able to reproduce the invalid input locally, I'll try to have it fixed by Monday's Beta 2 release. If not, I may ask for FTP access to debug it further :)
 
Last edited:
I have updated the files on my server using a freshly downloaded beta1 build. The importer seems to work great - I can see the rules transferred to dbseocp just fine. But there's an error in link creation:

forums links are missing [forum_title] variable at all. Custom rule for forum creation is [forum_title]-f[forum_id], the links are:
Code:
vbseo: http://test.babyboom.pl/forum/staramy-sie-f66/
dbseo: http://test.babyboom.pl/forum/-f66/

vbseo: http://test.babyboom.pl/forum/lipiec-2013-f484/
dbseo: http://test.babyboom.pl/forum/-f484/


threads: 
vbseo: http://test.babyboom.pl/forum/ciaza-porod-polog-f14/ciezaroweczki-po-vitro-51358-new/
dbseo: http://test.babyboom.pl/forum/-f14/ciae-a-ara-weczki-po-in-vitro-51358-new/

So it seems that the character replacement works as before.

My forum uses polish language with UTF-8 settings in Language manager
The database (MySQL 5.5.34 also uses UTF-8:
Code:
mysql> SELECT CCSA.character_set_name FROM information_schema.`TABLES` T,        information_schema.`COLLATION_CHARACTER_SET_APPLICABILITY` CCSA WHERE CCSA.collation_name = T.table_collation   AND T.table_schema = "babyboom"   AND T.table_name = "vb_thread";
+--------------------+
| character_set_name |
+--------------------+
| utf8               |
+--------------------+
1 row in set (0.00 sec)
I may open access to the test server, but it will take me a while. Just let me know if it's needed...
 
I have upgraded to beta 2 but my main issues are still not fixed.
1. Forum links don't contain [forum_title] part
2. accented characters are still messed during replacement - ciae-ara-weczki instead od ciezaroweczki when translating ciężaróweczki for example.

Code:
vbseo: http://test.babyboom.pl/forum/ciaza-porod-polog-f14/ciezaroweczki-po-vitro-51358-new/
dbseo: http://test.babyboom.pl/forum/-f14/ciae-ara-weczki-po-vitro-51358-new/
 
Okay, thanks for coming back to me. I will be taking a look at your site ASAP :)

At least the importer seems to have worked fine for you, so once I take care of those issues it should be sorted :)
 
Sorry to report, but it seems that only the first issue is fixed. I can see the title in forum urls, but the translation of accented characters is still not working as expected:
Code:
vbseo: http://test.babyboom.pl/forum/ciaza-porod-polog-f14/
dbseo: http://test.babyboom.pl/forum/ciae-pora-d-poa-g-f14/

vbseo: http://www.babyboom.pl/forum/ciaza-porod-polog-f14/ciezaroweczki-po-vitro-51358-new/
dbseo: http://test.babyboom.pl/forum/ciae-pora-d-poa-g-f14/ciae-ara-weczki-po-vitro-51358-new/

Any way I can assist you?
 
It was working fine after I left your test forum yesterday...

I re-uploaded the fixed files to your test forum and it is once again working.
 
Thanks. I didn't touch the files myself. Maybe a regression thing? Or something different. But it is working fine now. Thank you. I'll try to run source comparison with different pages and will post results.
 
I've been diffing two versions (dbseo/vbseo) of page source and I've made the following discoveries:
1. Vbseo seems to be adding -a- string in a thread url if the thread's title ends with a number. For example thread titled "GRA W SKOJARZENIA cz 2" becomes
Code:
vbseo: http://test.babyboom.pl/forum/pogaduszki-f74/gra-w-skojarzenia-cz-2-a-5801-new/
dbseo: http://test.babyboom.pl/forum/pogaduszki-f74/gra-w-skojarzenia-cz-2-5801-new/
2. Latest post with pagination links (checked in forumdisplay template):
Code:
vbseo: http://test.babyboom.pl/forum/dzieciaczki-f62/spis-forumowych-dzieciaczkow-1920/index56.html#post6997037
dbseo: http://test.babyboom.pl/forum/dzieciaczki-f62/spis-forumowych-dzieciaczkow-1920-post6997037/#post6997037
3. Latest post in thread - from forumdisplay:
Code:
vbseo: http://test.babyboom.pl/forum/dzieciaczki-f62/moje-male-madre-58142/#post8442892
dbseo: http://test.babyboom.pl/forum/dzieciaczki-f62/moje-male-madre-58142-post8442892/#post8442892

4. vbseo changes search form url, javascript libraries links etc to absolute urls, while dbseo doesn't. For example:
Code:
vbseo: <form action="http://test.babyboom.pl/forum/search.php
dbseo: <form action="search.php
5. Meta og:url wasn't replaced on displaythread:
Code:
vbseo: <meta property="og:url" content="http://test.babyboom.pl/forum/showthread.php?t=7492" />
dbseo: <meta property="og:url" content="http://test.babyboom.pl/forum/dzieciaczki-f62/kim-bede-gdy-dorosne-7492/" />
6. accented charactes problem in the following link (displaythread template):
Code:
vbseo: http://test.babyboom.pl/forum/dzieciaczki-f62/kim-bede-gdy-dorosne-7492/#post9933593
dbseo: http://test.babyboom.pl/forum/dzieciaczki-f62/kim-bae-dae-gdy-dorosnae-7492-post9933593/#post9933593

i will diff more pages tomorrow...
 
I've been diffing two versions (dbseo/vbseo) of page source and I've made the following discoveries:
1. Vbseo seems to be adding -a- string in a thread url if the thread's title ends with a number. For example thread titled "GRA W SKOJARZENIA cz 2" becomes
Code:
vbseo: http://test.babyboom.pl/forum/pogaduszki-f74/gra-w-skojarzenia-cz-2-a-5801-new/
dbseo: http://test.babyboom.pl/forum/pogaduszki-f74/gra-w-skojarzenia-cz-2-5801-new/
Hmm, I'm not sure if that's something that needs changing. If the URL still loads properly, it should be fine.

2. Latest post with pagination links (checked in forumdisplay template):
Code:
vbseo: http://test.babyboom.pl/forum/dzieciaczki-f62/spis-forumowych-dzieciaczkow-1920/index56.html#post6997037
dbseo: http://test.babyboom.pl/forum/dzieciaczki-f62/spis-forumowych-dzieciaczkow-1920-post6997037/#post6997037
3. Latest post in thread - from forumdisplay:
Code:
vbseo: http://test.babyboom.pl/forum/dzieciaczki-f62/moje-male-madre-58142/#post8442892
dbseo: http://test.babyboom.pl/forum/dzieciaczki-f62/moje-male-madre-58142-post8442892/#post8442892
If it's the "go to latest post" URL then I'd say the DBSEO URL is more correct, since it's referring to a specific post.

4. vbseo changes search form url, javascript libraries links etc to absolute urls, while dbseo doesn't. For example:
Code:
vbseo: <form action="http://test.babyboom.pl/forum/search.php
dbseo: <form action="search.php
5. Meta og:url wasn't replaced on displaythread:
Code:
vbseo: <meta property="og:url" content="http://test.babyboom.pl/forum/showthread.php?t=7492" />
dbseo: <meta property="og:url" content="http://test.babyboom.pl/forum/dzieciaczki-f62/kim-bede-gdy-dorosne-7492/" />
I believe these have already been taken care of, as they're working fine locally for me.

6. accented charactes problem in the following link (displaythread template):
Code:
vbseo: http://test.babyboom.pl/forum/dzieciaczki-f62/kim-bede-gdy-dorosne-7492/#post9933593
dbseo: http://test.babyboom.pl/forum/dzieciaczki-f62/kim-bae-dae-gdy-dorosnae-7492-post9933593/#post9933593
Was this checked after the fixes I made?
 
Hmm, I'm not sure if that's something that needs changing. If the URL still loads properly, it should be fine.

If the goal is to have a 100% translation of vbseo urls to dbseo, then I'd say you should at least translate the vbseo url into a new one using 301 redirect... In my case there's a lot of threads ending with a year (2011, 2012 etc) and these would be lost for Google if I'd move to dbseo.

If it's the "go to latest post" URL then I'd say the DBSEO URL is more correct, since it's referring to a specific post.
I'd beg to differ. vbseo's version keeps a standard thread url, adding the specific as an anchor at the end. dbseo's version modifies the thread url, de facto leading to a different url
Code:
http://test.babyboom.pl/forum/dzieciaczki-f62/moje-male-madre-58142/ 
suddenly becomes 
http://test.babyboom.pl/forum/dzieciaczki-f62/moje-male-madre-58142-post8442892/
AFAIR vbseo's goals were to limit the amount of urls a specific content may exist under. With your urls - search engine is suddenly presented with a completely different url for a whole thread.

I believe these have already been taken care of, as they're working fine locally for me.
It's not fixed in my 1.0.0.b3 - I still get
Code:
<meta property="og:url" content="http://test.babyboom.pl/forum/showthread.php?t=54299">
in thread view.
Another problem is that with vbseo og tags are specific for each forum. With dbseo I only get a homepage og tags on each display forum page.

Was this checked after the fixes I made?
Those were checked after your fixes but before beta 3 which seems to fix them.

As a side note - I've had to close access to the test site (because some spiders started to index the pages regardless of the robots.txt settings). Drop me a note if you need access.
 
Last edited:
I'd beg to differ. vbseo's version keeps a standard thread url, adding the specific as an anchor at the end. dbseo's version modifies the thread url, de facto leading to a different url
Firstly, that's incorrect. vBSEO is simply bugged in that it does not respect its own "Go to post" URL setting.

Secondly, if you would like to change this, you can customise the "Thread Go To Post URL" setting and remove the "post[post_id]" reference from that URL format. Keep in mind that by doing this, you may reduce functionality in certain aspects.

Having the option for a separate URL for permalinks to a certain post that is not dependant on the anchor is a feature, not a bug. The fact that there is a canonical URL tag in the source of the showthread page means that duplicate content issues are non-existent.

It's not fixed in my 1.0.0.b3 - I still get
Code:
<meta property="og:url" content="http://test.babyboom.pl/forum/showthread.php?t=54299">
in thread view.
In your previous post, you said that vBSEO did not change the og:url and DBSEO does change it. I checked the source of the threads and DBSEO does not change it for me, leading me to believe it's fixed in the internal development build.

You now appear to be saying that DBSEO should change the URLs. Please clarify.

Another problem is that with vbseo og tags are specific for each forum. With dbseo I only get a homepage og tags on each display forum page.
I don't understand what you mean by this, please clarify.
 
Firstly, that's incorrect. vBSEO is simply bugged in that it does not respect its own "Go to post" URL setting.
Secondly, if you would like to change this, you can customise the "Thread Go To Post URL" setting and remove the "post[post_id]" reference from that URL format. Keep in mind that by doing this, you may reduce functionality in certain aspects.
Having the option for a separate URL for permalinks to a certain post that is not dependant on the anchor is a feature, not a bug. The fact that there is a canonical URL tag in the source of the showthread page means that duplicate content issues are non-existent.

OK - I haven't thought of canonical. Thanks for clearing this up. Replacing vbseo is a huge undertaking for me. I have a large website and a lot of indexed content. I don't want to lose any traffic bacause of vbseo being replaced. I have no problem with urls being changed in the process as long as there is a way to create a backup set of redirects for Google traffic. Before I replace vbseo I need to be 100% sure that every incoming link I've beuilt in the past years will keep working.

In your previous post, you said that vBSEO did not change the og:url and DBSEO does change it. I checked the source of the threads and DBSEO does not change it for me, leading me to believe it's fixed in the internal development build.
You now appear to be saying that DBSEO should change the URLs. Please clarify.
I don't understand what you mean by this, please clarify.

I'm sorry for not being clear.
In dbseo beta3 on my test forum og: tags behave like this:
on forum homepage: og tags are correct
on forum id=X: I get og:title, og:description, og:url from forum homepage and not from the current forum
on thread id=X: I get proper title and description but NOT transformed url
Code:
http://test.babyboom.pl/forum/showthread.php?t=277
 
I'm sorry for not being clear.
In dbseo beta3 on my test forum og: tags behave like this:
on forum homepage: og tags are correct
on forum id=X: I get og:title, og:description, og:url from forum homepage and not from the current forum
on thread id=X: I get proper title and description but NOT transformed url
Code:
http://test.babyboom.pl/forum/showthread.php?t=277
I'm still a bit confused.

Can you please post the differences between vBSEO and DBSEO for those pages? I'll compare the links to what I'm seeing here on DBT, as I can't activate Facebook integration on my local computer.
 
Can you please post the differences between vBSEO and DBSEO for those pages? I'll compare the links to what I'm seeing here on DBT, as I can't activate Facebook integration on my local computer.

Sure:
Code:
http://test.babyboom.pl/forum/:
dbseo:
<meta property="fb:app_id" content="37767549361" />
<meta property="og:site_name" content="Forum BabyBoom" />
<meta property="og:description" content="Forum dla przyszłych i obecnych rodziców. Tematy: poróda, ciąża, przebieg ciąży, dzieci, niemowlęta, wychowanie, rodzina." />
<meta property="og:url" content="http://test.babyboom.pl/forum" />
<meta property="og:type" content="website" />

vbseo:
<meta property="fb:app_id" content="37767549361" />
<meta property="og:site_name" content="Forum BabyBoom" />
<meta property="og:description" content="Forum dla przyszłych i obecnych rodziców. Tematy: poróda, ciąża, przebieg ciąży, dzieci, niemowlęta, wychowanie, rodzina." />
<meta property="og:url" content="http://test.babyboom.pl/forum/" />
<meta property="og:type" content="website" />




http://test.babyboom.pl/forum/ciaza-porod-polog-f14/:
dbseo:
<meta property="fb:app_id" content="37767549361" />
<meta property="og:site_name" content="Forum BabyBoom" />
<meta property="og:description" content="Forum dla przyszłych i obecnych rodziców. Tematy: poróda, ciąża, przebieg ciąży, dzieci, niemowlęta, wychowanie, rodzina." />
<meta property="og:url" content="http://test.babyboom.pl/forum" />
<meta property="og:type" content="website" />
vbseo:
<meta property="fb:app_id" content="37767549361" />
<meta property="og:site_name" content="Forum BabyBoom" />
<meta property="og:description" content="Ciąża, poród, połóg - Wszystko o ciąży, porodzie i połogu." />
<meta property="og:url" content="http://test.babyboom.pl/forum/ciaza-porod-polog-f14/" />
<meta property="og:type" content="website" />


http://test.babyboom.pl/forum/ciaza-porod-polog-f14/ciaza-dentysta-25936/:
dbseo:
<meta property="fb:app_id" content="37767549361" />
<meta property="og:site_name" content="Forum BabyBoom" />
<meta property="og:description" content="DZIEWCZYNY ZA DWIE GODZINY, O 16 MAM USUNAC ZABKA-6.POWIEDZCIE CZY MOGE ???????JESTEM W POLOWIE 10 TYG CIAZY.PROSZE O OPINIE" />
<meta property="og:url" content="http://test.babyboom.pl/forum/showthread.php?t=25936" />
<meta property="og:type" content="article" />

vbseo:
<meta property="fb:app_id" content="37767549361" />
<meta property="og:site_name" content="Forum BabyBoom" />
<meta property="og:description" content="DZIEWCZYNY ZA DWIE GODZINY, O 16 MAM USUNAC ZABKA-6.POWIEDZCIE CZY MOGE ???????JESTEM W POLOWIE 10 TYG CIAZY.PROSZE O OPINIE" />
<meta property="og:url" content="http://test.babyboom.pl/forum/ciaza-porod-polog-f14/ciaza-dentysta-25936/" />
<meta property="og:type" content="article" />
 
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,172
Customer rating
5.00 star(s) 1 ratings
Back
Top