Uutiset:

SMF 2.1.4 has been released! Take it for a spin! Read more.

Main Menu
Advertisement:

KABLOOEY! Upgraded and killed SMF!

Aloittaja sursum, toukokuu 14, 2006, 09:46:19 IP

« edellinen - seuraava »

sursum

SMF Version: SMF 1.1 RC1
Hello,

I'm having multiple problems with a new SMF installation.  Here's the chain of events:

1.  I installed a 1.0.7. version and got it up and running fine.
2.  I installed the Mambo "com_smf" component to integrate it into Mambo.  PROBLEM #1: The SMF theme stylesheet was overriding the Mambo stylesheet in most respects.
3.  Thinking the Mambo stylesheet problem may be due to a version conflict, I upgraded the 1.0.7 install to the 1.1 RC1 by uploading all the files into the same directory, accessing upgrade.php, following the directions, and finally getting a "Upgrade successful" notice.  PROBLEM #2: SMF is now completely non-functional, and not even loading fully.  You can see the problem here... hxxp:charmedlabsc.temp.powweb.com/discuss/ [nonactive] .  I'm also now getting a huge error message

LainaaSorry, the copyright must be in the template.
Please notify this forum's administrator that this site is using an ILLEGAL copy of SMF!

Which can't be right since I downloaded the upgrade on the SMF site and installed it using the upgrade.php file to install.

Any help?

sursum

Please disregard.

Due to time constraints, I'm having to go with another solution.

Oldiesmann

What "time constraints"? You posted at 9:45PM on a Sunday night - a time when there won't be as many people online who can answer your questions. Please be patient with us if you should ever decide to come back. In this case if you had simply re-uploaded your theme files, the problem probably would have gone away.
Michael Eshom
Christian Metal Fans

sursum

Nothing negative intended in that at all!  I was just giving a heads up to let you know not to spend time working a solution for me.  Didn't want to waste anyone's time.   ;)

I think SMF is a great product, but I realized there are more obstacles ahead than just getting the installation right.  I was faced with:

1.  First, I'd have to upgrade phpBB on the old server so that its version would match the new version on the new server.
2.  After upgrading, export the data.
3.  Install the new version of phpBB on the new server (since the data convertor requires that the phpBB installation is on the same root).
4.  Install SMF (properly) on the new server.
5.  Run the phpBB data conversion to SMF.
6.  Integrate it with com_smf into Mambo (problem here since the instructions say to install SMF on the same database as Mambo.  I'm using Powweb hosting and they don't give you a choice of which database.  You simply install and see where they put it.)
7.  Work out the template problems where the SMF stylesheet is overriding the Mambo stylesheet despite being pulled in as a component.

So, because of all the above, it's easier for me just to install phpBB on the new server and leave it at that.

I'll definitely be looking into SMF in the future... particulary for new forums that won't require migrating any data over.  Still not sure how to work around the problem of needing to install SMF on the same database as Mambo, though.  Something to look into.

Thanks for your response.





Oldiesmann

If you install Mambo and/or SMF manually (ie not through an auto-install package), there's nothing to prevent you from installing them on the same database. Also, it's not quite as complicated as you think - install SMF on the old server and convert to SMF there. Install SMF on the new server using the same database prefix, then go into phpMyAdmin and drop all the SMF tables. Export the SMF database on the old server (table structure and all) then import it through phpMyAdmin on the new server.

SMF's stylesheet should only override Mambo's stylesheet for SMF itself - this was done on purpose because SMF looks weird if it's forced to use Mambo's stylesheet. Orstio should be able to help you with that though.

I'm also pretty sure that the integration will run on two seperate databases - as long as you can assign the same MySQL user to both databases, you shouldn't have too many problems.
Michael Eshom
Christian Metal Fans

Advertisement: