Google search result links to old site don't work

[jtorral]

The old google search results do not work on the new site even though the threads are there.

Yes. Using the original .htaccess prvided with the software.

here is an example

https://www.rangefinderforum.com/for...8&page=4%C2%A0

[Wayne Luke]

What are the results of the following query:

SELECT nodeid, title FROM node WHERE oldid=167468

You can run queries within the vBulletin Admin Control Panel by going to Maintenance -> Execute SQL Queries.

To run Queries in the Admin Control Panel you need to edit your config.php file and add your user ID to the Can Run Queries section. It looks like:

	//	****** USERS WITH QUERY RUNNING PERMISSIONS ******
	//	The users specified here will be allowed to run queries from the control panel.
	//	See the above entries for more information on the format.
	//	Please note that the ability to run queries is quite powerful. You may wish
	//	to remove all user IDs from this list for security reasons.
$config['SpecialUsers']['canrunqueries'] = '';

Place your user id between the single quotes.

[jtorral]

MariaDB [rff]> SELECT nodeid, title FROM node WHERE oldid=167468;
+--------+-----------------------------------------------------+
| nodeid | title |
+--------+-----------------------------------------------------+
| 170614 | Ultron 35mm f2 Aspherical vs Summicron 35mm f2 ASPH |
| 403908 | |
+--------+-----------------------------------------------------+
2 rows in set (4.696 sec)

MariaDB [rff]>

[Wayne Luke]

Hmm. There should only be a single entry. When you upgraded were there any issues with the process?

[jtorral]

no. went through just fine.


select oldid, count(*) from node group by 1 having count(*) > 1;

here are just a few before query died.


| 848581 | 2 |
| 848582 | 2 |
| 848583 | 2 |
| 848585 | 2 |
| 848586 | 2 |
| 848587 | 2 |
| 848588 | 2 |
| 848589 | 2 |
| 848590 | 2 |
| 848591 | 2 |
| 848592 | 2 |
| 848593 | 2 |
| 848594 | 2 |
+--------+----------+
313275 rows in set (2 min 27.158 sec)

Here is one example of a duplicate


MariaDB [rff]> select * from node where oldid = 848594 \G
*************************** 1. row ***************************
nodeid: 1335597
routeid: 107
contenttypeid: 27
publishdate: 1214966237
unpublishdate: 0
userid: 5576
groupid: NULL
authorname: mike kim
description: NULL
title:
htmltitle:
parentid: 62420
urlident: NULL
displayorder: NULL
starter: 62420
created: 1214966237
lastcontent: 1214966237
lastcontentid: 1335597
lastcontentauthor:
lastauthorid: 0
lastprefixid:
textcount: 0
textunpubcount: 0
totalcount: 0
totalunpubcount: 0
ipaddress: 200.114.191.241
showpublished: 1
oldid: 848594
oldcontenttypeid: 1
nextupdate: NULL
lastupdate: NULL
featured: 0
CRC32: 3754866789
taglist: NULL
inlist: 1
protected: 0
setfor: 0
votes: 0
hasphoto: 0
hasvideo: 0
deleteuserid: NULL
deletereason: NULL
open: 1
showopen: 1
sticky: 0
approved: 1
showapproved: 1
viewperms: 2
commentperms: 1
nodeoptions: 138
prefixid:
iconid: 0
public_preview: 0
*************************** 2. row ***************************
nodeid: 4742505
routeid: 59
contenttypeid: 22
publishdate: 1632404903
unpublishdate: NULL
userid: 71424
groupid: NULL
authorname: punkzter
description: DAG
title: DAG
htmltitle: NULL
parentid: 8
urlident: NULL
displayorder: NULL
starter: 4742505
created: 1632404903
lastcontent: 1633387451
lastcontentid: 4751635
lastcontentauthor: punkzter
lastauthorid: 71424
lastprefixid:
textcount: 2
textunpubcount: 0
totalcount: 2
totalunpubcount: 0
ipaddress:
showpublished: 1
oldid: 848594
oldcontenttypeid: 9989
nextupdate: NULL
lastupdate: NULL
featured: 0
CRC32:
taglist: NULL
inlist: 0
protected: 1
setfor: 0
votes: 0
hasphoto: 0
hasvideo: 0
deleteuserid: 0
deletereason: 0
open: 1
showopen: 1
sticky: 0
approved: 1
showapproved: 1
viewperms: 2
commentperms: 1
nodeoptions: 138
prefixid:
iconid: 0
public_preview: 0
2 rows in set (12.977 sec)

[Wayne Luke]

I am going to have to discuss this with the developers.

[jtorral]

thanks. Please get back to me.

[Wayne Luke]

Do you have a pre-upgrade database? We need to try and recreate the problem.

[jtorral]

I can provide you a mysqldump of the DB. Please advise what next. Obviously I wont put it here

Thanks

[Wayne Luke]

The general recommendation is to make the file available on your favorite sharing site and provide us a link by creating a support ticket. The link is in the footer of the page. Reference this topic in the support ticket so we can complete the loop.

We can also grab the file using SFTP or FTPS if you want to make it available on your server.

[jtorral]

is there a query you can supply to delete the required duplicates or fix the issue?

[Wayne Luke]

Unfortunately, the answer is "not really!"

The problem here is that every node has multiple entries in the closure table and a linked entry in the text table. Unfortunately, the system doesn't use referential integrity (even though it uses transactions on submission). If there were proper foreign keys and referential integrity defined, then I could give a simple query. Since it isn't, it would need code written to actually manage the deletions to make sure that things work properly afterwards.