vBulletin 4.1.12 - Promote Post to Article "Page not found" error

Since upgrading to vBulletin 4.1.12 I can't promote a post/thread to an article as it gives me a blank page with the "Page not found" error and the article is not posted.

If I disable vBSEO it all works fine again. I've sent a ticket but thought best to mention here should anyone else be having issues.

Please don't double post both in ticket and thread. As explained you within your ticket , the issue you mention functions 100% correct on vBSEO.com which means the issue is 100% related to your configuration. Please either stick to this forum post or respond within your ticket. Creating duplicate thread will just double our work load.

I posted here to see if anyone else was having the same issue as me. I apologise for using your forum as a forum.

Nothing has changed with my configuration apart from updating to vB 4.1.12. If I turn off vBSEO this issue goes away.

All previous versions of vBulletin (4.1.11 down) worked fine. I'll continue using the support ticket.

I have been asked VBSEO team since beta version (this thread) and there are still issue on final version of 4.1.12 too.

Originally Posted by Baanfarsang

I have been asked VBSEO team since beta version (this thread) and there are still issue on final version of 4.1.12 too.

Promoting posts to articles function 100% correct on vBSEO.com , if you are facing an issue , that can highly be related to vbulletin or any modification you are using. It can also be related to vBSEO but without examining further this on a site that face the issue , there is nothing we can say.

It's just odd. All I did was upgrade from 4.1.11 to 4.1.12 and i've not changed anything. Turning off vBSEO the error goes away. I'll just have to turn on and off when I post an article then.

Please create a ticket with login details so we can investigate further

Originally Posted by Mert Gökçeimam

Promoting posts to articles function 100% correct on vBSEO.com , if you are facing an issue , that can highly be related to vbulletin or any modification you are using. It can also be related to vBSEO but without examining further this on a site that face the issue , there is nothing we can say.

I used all strings you defined as CMS URLs such:

Sample custom string:
cmssection-[section_id]-list[page].html

Sample custom string:
content.html



Do you want to visit my AdminCP and try to promote any threads to article?

Originally Posted by Mert Gökçeimam

Please create a ticket with login details so we can investigate further

I've updated my previous ticket with the info you need.

Also I have found the problem.
In my case the problem does not occur if the first I press the button apply and then save, but if I proceed with the save directly tells me page not found

I hope can be useful

regards

I have the same problem, to publish an article i turn off VBSEO, publish, and then re-active vBSEO

Any Solution?

Thanks

Originally Posted by Neal

Since upgrading to vBulletin 4.1.12 I can't promote a post/thread to an article as it gives me a blank page with the "Page not found" error and the article is not posted.

Hello Alessandro ,

Please try following

find the following in vbseo/includes/functions_vbseo.php

PHP Code:

if($preurl[strlen($preurl)-1]=='"' && (($qpos = strpos($posturl,'"'))>0) && ($posturl[0]!="'"))
{
$url .= substr($posturl, 0, $qpos);
$posturl = substr($posturl, $qpos);
} 


add below

PHP Code:

$is_formpost = strstr($posturl, 'method="post"'); 


find:

PHP Code:

if(VBSEO_REWRITE_CMS) 


replace with:

PHP Code:

if(VBSEO_REWRITE_CMS && !$is_formpost) 


find:

PHP Code:

if(VBSEO_REWRITE_CMS && VBSEO_VB4 && in_array(VB_ROUTER_SEGMENT, array('list', 'content'))) 


replace with:

PHP Code:

if((!$_POST || count($_POST)<2) && VBSEO_VB4 && in_array(VB_ROUTER_SEGMENT, array('list', 'content'))) 


Hello Mert,
The third code says my editor (dreamweaver) that there is a syntax error.
If i copy the edited file, i get blank page for each topic you select.

Thx

Nothing?

Thank you

Please try to wait before bumping tickets , the edit is correct and there is nothing wrong with the last line.