Bug DBSEO two problem

[kakalot]

Dear Sir/Madam,

I just purchased and installed the DBSEO version 1.2.7 and now I'm facing with two problem, my website got three database (1 master and two read only slaves):

1. When presistent URL option enable, DBSEO will try to insert into table dbseo_resolvedurl of the read only slave database instead of master leading my forum to throw out an error that cannot write to --read-only database.

here is the sql insert query from you url.php file:

DBSEO::$db->modifyQuery('
                                                                INSERT INTO $dbtech_dbseo_resolvedurl
                                                                        (forumurl, seourl, urldata, format)
                                                                VALUES (
                                                                        \'' . DBSEO::$db->escapeString($successfulUrl) . '\',
                                                                        \'' . DBSEO::$db->escapeString($url) . '\',
                                                                        \'' . DBSEO::$db->escapeString(trim(serialize($urlMatch['info']))) . '\',
                                                                        \'' . DBSEO::$db->escapeString($urlMatch['format']) . '\'
                                                                )
                                                        ');
                                                }
                                        }

2. When I rename the thread title, DBSEO won't rewrite the old thread title URL to the new one, I will make my forum have to same content URL with one is old thread title url and one is new thread title url. That caused alot of duplicate content to my site.
for example old url is :
https://www.5giay.vn/mobile/7343801...ghz-qualcomm-snapdragon-800-full-hd-32gb.html

now if I rename this thread title by replace snapdragon 800 with snapdragon 1000, DBSEO will made two URL that not redirect old to the new one with this two URL:
https://www.5giay.vn/mobile/7343801...ghz-qualcomm-snapdragon-800-full-hd-32gb.html
https://www.5giay.vn/mobile/7343801...hz-qualcomm-snapdragon-1000-full-hd-32gb.html

this problem was not happen with VBSEO that I used before.

Could you please take a look and make it fixed ?

P/S: I also notice and wonder will this query in file class_core.php cause the insert into my read-only slave mysql DB?

 self::$db->modifyQuery('
                                INSERT INTO $dbtech_dbseo_spiderlog
                                        (dateline, spider, script, hits)
                                VALUES (
                                        ' . $date . ',
                                        \'' . self::$db->escapeString(DBSEO_SPIDER) . '\',
                                        \'' . self::$db->escapeString($script) . '\',
                                        1
                                )
                                ON DUPLICATE KEY UPDATE hits = hits + 1
                        ');

Best Regards.

 

[Fillip H.]

1. When presistent URL option enable, DBSEO will try to insert into table dbseo_resolvedurl of the read only slave database instead of master leading my forum to throw out an error that cannot write to --read-only database.

This means your vBulletin config.php file is not set up correctly. Any query passed to modifyQuery will be handled by the Master server. In vBulletin's config.php, by default it supports 1 master and 1 slave, which is what DBSEO also supports

2. When I rename the thread title, DBSEO won't rewrite the old thread title URL to the new one

If you either manually clear your cache via the DBSEO CP, or wait for it to expire normally, it will indeed redirect the old URL to the new canonical URL

 

[kakalot]

Dear Sir,

I can be sure that my config.php is correctly for over 4 years and everything working perfectly write to the correct master until I move from VBSEO to DBSEO.

Here is my config.php databsae section:

	//	****** DATABASE TYPE ******
	//	This is the type of the database server on which your vBulletin database will be located.
	//	Valid options are mysql and mysqli, for slave support add _slave.  Try to use mysqli if you are using PHP 5 and MySQL 4.1+
	// for slave options just append _slave to your preferred database type.
$config['Database']['dbtype'] = 'mysqli_slave';

	//	****** DATABASE NAME ******
	//	This is the name of the database where your vBulletin will be located.
	//	This must be created by your webhost.
$config['Database']['dbname'] = 'web24db1';

	//	****** TABLE PREFIX ******
	//	Prefix that your vBulletin tables have in the database.
$config['Database']['tableprefix'] = '';

	//	****** TECHNICAL EMAIL ADDRESS ******
	//	If any database errors occur, they will be emailed to the address specified here.
	//	Leave this blank to not send any emails when there is a database error.
$config['Database']['technicalemail'] = '';

	//	****** FORCE EMPTY SQL MODE ******
	// New versions of MySQL (4.1+) have introduced some behaviors that are
	// incompatible with vBulletin. Setting this value to "true" disables those
	// behaviors. You only need to modify this value if vBulletin recommends it.
$config['Database']['force_sql_mode'] = false;



	//	****** MASTER DATABASE SERVER NAME AND PORT ******
	//	This is the hostname or IP address and port of the database server.
	//	If you are unsure of what to put here, leave the default values.
$config['MasterServer']['servername'] = '192.168.20.7';
$config['MasterServer']['port'] = 3306;

	//	****** MASTER DATABASE USERNAME & PASSWORD ******
	//	This is the username and password you use to access MySQL.
	//	These must be obtained through your webhost.
$config['MasterServer']['username'] = 'web24u1';
$config['MasterServer']['password'] = 'xxxxxxx';

	//	****** MASTER DATABASE PERSISTENT CONNECTIONS ******
	//	This option allows you to turn persistent connections to MySQL on or off.
	//	The difference in performance is negligible for all but the largest boards.
	//	If you are unsure what this should be, leave it off. (0 = off; 1 = on)
$config['MasterServer']['usepconnect'] = 1;



	//	****** SLAVE DATABASE CONFIGURATION ******
	//	If you have multiple database backends, this is the information for your slave
	//	server. If you are not 100% sure you need to fill in this information,
	//	do not change any of the values here.
$config['SlaveServer']['servername'] = '192.168.20.13';
$config['SlaveServer']['port'] = 3305;
$config['SlaveServer']['username'] = 'web24u3';
$config['SlaveServer']['password'] = 'xxxxxx';
$config['SlaveServer']['usepconnect'] = 0;

 

[kakalot]

This is an error that it apear:

Invalid query: The MySQL server is running with the --read-only option so it cannot execute this statement106

 

[Fillip H.]

I've re-worked the database connection in DBSEO, but I'd like to visit your site to implement it - I don't want to add it to the "live" release until I've tested it on a setup like yours.

Would you be willing to give me FTP information so that I can implement these changes on your site?

 

[kakalot]

hi Sir,

My company policy is not allowing giving out ftp passowrd, could you please send the fixed code to me and I will test by myself ?

Best Regards.

 

[Fillip H.]

In that case, I've simply uploaded the fixes to the v1.2.8 release. If you re-download the product and re-upload the files, let me know if there are any issues. I recommend putting your forum in maintenance mode until you have completed your testing, in case the fix doesn't work or there are any other issues.