Thread Starter
Anonymous
Mine neither
I made a fresh install and got this
Parse error: parse error in /home/(websiteName)/public_html/(installDirectory)/wp-admin/upgrade-functions.php on line 825
And to think I survived MT’s installation.. I must have missed something obvious… thanks in advance! 🙂
Which version are you trying to install? Looks like the files are wrong, cause the wordpress files are prefixed with wp, instead of b2.
Thread Starter
Anonymous
Btw, I have webhosting with Fantastico which has an automatic installation of WP but is version 1.01, I tried upgrading to no avail. I’m seriously missing something here (I did read the readme file). Maybe it’s just not my day…
Pete
ps. Oh! And the above post with the parse error 825 is mine too
Pete,
After uploading all of the new files for the upgrade, did you run /wp-admin/upgrade.php?
Just had to ask. 🙂
Thread Starter
Anonymous
lol yeah luckily I’m not that gone.. the first time I used the Fantastico’s automatic script to install WP on my server, which worked as expected then I uploaded the files to the same folder (overwriting everything) and ran /wp-admin/upgrade.php? but it didn’t work so I tried installing from scratch which gave me the parse error 825
Pete
Maybe I’m not understanding this correctly, but if you’re doing a fresh install, shouldn’t you be using install instead of upgrade?
No. You need to do the install AND then run upgrade. Dont ask why. HTH 😉
Actually you can have any number of different layouts for subcategories, you just need to build the templates. I have different templates for my About, Archives Index, and Photos pages. You simply make a copy of index.php for each, rename it to say archives.php for your Archives Index, customize, and then modify the category mod_rewrite rule so that archive directories use say archives.php instead of index.php.
Not trying to single you out, but I think a lot of users coming from MT have difficulty picking up the WP architecture and the mod_rewrite rules. These rules essentially serve the dual purpose of specifying the directory structure of your archives and which template to use. If you peek in the .htaccess you’ll see that every archive rule makes use of index.php. Once you change that to another file, you’ve begun using a new template.
About the 825. I looked it up here and line 825 is only called for upgrades.
cleanhttp://www.junesix.org/xref/beta/nav.php?wp-admin/upgrade-functions.php.source.php#l825
If you have direct ftp access, why not bypass Fantastico altogether? Clean out everything in the root dir where you want WP (except files/directories your host put there). Upload 1.2 and just run the 5-min install. If you get the 825 again, something has gone wrong because upgrade-functions.php should not be used at all for fresh installs.
“then modify the category mod_rewrite rule so that archive directories use say archives.php instead of index.php.”
Can someone post their “mod_rewrite” rules as an example?
Make a copy of index.php and name it archive.php. In your .htaccess file, change line 4 from
RewriteRule ^archives/category/?(.*) /index.php?category_name=$1 [QSA]
to
RewriteRule ^archives/category/?(.*) /archive.php?category_name=$1 [QSA]
Now archive.php is your template for archive pages. Customize it as desired.
This is great news. I’ll be playing a bit with the templates then and see if I get them to work.
I was about to use nucleus because of the native support for categories, subtegories, weblogs within weblogs, and different templates for categories. Luckily I didn’t start yet.
