I tried upgrading and doing a fresh install of VBSEO 3.5 RC2 on my vB 4.0.1 board. Afterwords the CMS page is broken, displaying only text and no layout or graphics. Any suggestions?
This is a discussion on VBSEO 3.5 RC2 Break 4.0.1 CMS within the Troubleshooting forums, part of the vBSEO SEO Plugin category; I tried upgrading and doing a fresh install of VBSEO 3.5 RC2 on my vB 4.0.1 board. Afterwords the CMS ...
I tried upgrading and doing a fresh install of VBSEO 3.5 RC2 on my vB 4.0.1 board. Afterwords the CMS page is broken, displaying only text and no layout or graphics. Any suggestions?
Hello,
Does it work correctly if you disable vBSEO?
The Forum Hosting - Forum Hosting from the Forum Experts
As your vb install is in /forums, simply copying the vb index file to root will always have that effect.
Since you are only using vb now, i would suggest migrating to root as outlined here:
Moving to forum root
Brian Cummiskey / Crawlability Inc.
Security vbulletin - Patch Level for all supported versions released!
Unveiling the NEW vBSEO Sitemap Generator 3.0. - available NOW for vBSEO Customers!
What do you mean "only using vB now"?
In any event I copied everything over and put the .htaccess file in the /forums folder. It looks like it's working, but now the URL shows "genrefinity.net/content" as opposed to "genrefinity.net" like I had it. Any suggestions on getting it back to just the domain and dropping the /content but still have people access the CMS page first?
UPDATE #1: Scratch that. I can't reply or post new articles or threads now.
UPDATE #2: I think I fixed it. I changed the "forum" path in the vB CP and that seems to have done the trick for replying and posting. The /content problem is still there though.
Please see this post for instructions on how to remove /content
vBSEO 3.5 Release Candidate 1 is here!
Brian Cummiskey / Crawlability Inc.
Security vbulletin - Patch Level for all supported versions released!
Unveiling the NEW vBSEO Sitemap Generator 3.0. - available NOW for vBSEO Customers!
I'm having this same issue. My VB install has been in /forum for going on 6 years. Migrating to root is not really an option for me as I'd have a jillion broken image links.
I don't mind keeping the /forum heirarchy - It's just that when I activate VBSEO it breaks the index.php VBulletin provides to get around this issue.
I actually posted this in another thread. only spotted this one now. I have the same problem. How can i fix it.
I need cms in root and forum in /forums
Once vBseo is enabled, it breaks my index.php
http://www.unitethecows.com - P2P & Digital Media Forum
I love how the only real suggestion thus far has been "migrate to root". I'd wager most who've been running VB more than a couple of years has VB installed in /forum or /forums, especially those who ran VBAdvanced CMS in the past.
Following the instructions here :vBSEO 3.5 Release Candidate 1 is here! doesn't help in the least.
I thought my install had gone flawlessly, even going out for a bit afterwards, only to come back and try to access my site via siteroot. (http://www.mydomain.com).
I've found a temporary solution is to redirect siteroot to /forum(s) if you wish to leave VBSEO enabled.
I still would like a real solution, a redirect is not the answer.
Brian Cummiskey / Crawlability Inc.
Security vbulletin - Patch Level for all supported versions released!
Unveiling the NEW vBSEO Sitemap Generator 3.0. - available NOW for vBSEO Customers!
Brian,
I have followed the below instructions, but it does not work for me.
Can you assist me please? I would be happy to get the above method working. My site has been closed all weekend and I really want to get this fixed up today,/forums (or another folder name) vb4 install
Puts the CMS in root, outside of your forums folder, with no /content/ redirect and your forums remain in their subfolder as always.
Step 1
Physically move forums/index.php to your root directory.
Make sure index.php is set to require Content.
Code:
require('content.php');
and that the forum require code bit is commented out.
Step 2:
rename forums/index.php to forums/index_old.php or some other name to keep it around, but not named index.
Step 3:
rename forums/forum.php to forums/index.php
Step 4:
In vBoptions => forumhome Page options
set the first entry to
Code:
index
And in vboptions -> CMS options,
Make sure the 'site tab URL' script is
Code:
content.php
Step 5:
in vbseocp
URL Reweite Settings -> CMS => Advanced Settings tab
set CMS Home
to your FULL .com root with trailing slash, aka
Code:
http://www.yourdomain.com/
DO NOT screw up your www's here. Use them or don't use them as your htaccess and vboptions for BBURL are EXACTLY set up, or you'll end up in a loop.
Step 5:
In vbseocp, Seo Functions -> Homepage settings
set Force forum root as homepage to Yes
and enter
Code:
forums/index.php
forums/index.php?
in the aliases box.
Save settings.
Done.
/ => CMS
/forums/ = forum home
Do I need to move to root? If If I have to I will. However, I was hoping for another solution as my forums have been in /forums/ for 8 years.
http://www.unitethecows.com - P2P & Digital Media Forum
What doesn't work about it? I have installed to that exact method and it is working.
Brian Cummiskey / Crawlability Inc.
Security vbulletin - Patch Level for all supported versions released!
Unveiling the NEW vBSEO Sitemap Generator 3.0. - available NOW for vBSEO Customers!
I have sent you a PM so you can have a look. It still breaks my index.php
http://www.unitethecows.com - P2P & Digital Media Forum
So I gave up on this and moved everything to the root by using Brians guide above. I also used the Moving to forum root to redirect everything else to the correct place.
I'll probably lose some rankings, but hey, it's a move I hope will save me hassle in the long run!
http://www.unitethecows.com - P2P & Digital Media Forum
What doesn't work for me is /index.php. Nothing else seems to be broken, and I've gone over those instructions 15 times (literally).
What happens is when accessing siteroot/index.php, the cms is broken and all links point to /blog.php, /post.php, instead of /forum/blog.php, /forum/post.php, etc.
I assume this is "normal" - assuming the redirects are working. Some path or redirect issue is amiss.