Oh boy!
Well, I have little familiarity with what makes Chyrp tick. For most web projects, guides for upgrading are useful. The Chyrp attitude is, run git on your server (I can't with dreamhost! It won't compile!), and use that to update. Well, I tried once before, and decided not to update. Today I tried again, with a better backup system (tarred it!) and went for it again. Used git here on my mac, made a tar.bz2, uploaded that, extracted, moved the proper files (.htaccess, /config/database.yaml.php, /config/config.yaml.php) over, and went from there. That worked, except for some issues with tags.
Good thing I made a new directory, too, because several things were relocated!
rename themes/default/{ => content}/sidebar.twig (100%)
create mode 100644 themes/default/feathers/audio.twig
rename themes/default/{content => }/feathers/chat.twig (58%)
create mode 100644 themes/default/feathers/link.twig
create mode 100644 themes/default/feathers/photo.twig
rename themes/default/{content => }/feathers/quote.twig (65%)
rename themes/default/{content => }/feathers/text.twig (56%)
create mode 100644 themes/default/feathers/video.twig
rename themes/default/{content => pages}/404.twig (100%)
rename themes/default/{content => pages}/archive.twig (94%)
rename themes/default/{content => pages}/drafts.twig (81%)
rename themes/default/{content => pages}/feather.twig (83%)
create mode 100644 themes/default/pages/index.twig
rename themes/default/{content => pages}/search.twig (84%)
rename themes/default/{content => pages}/tag.twig (85%)
rename themes/default/{content => pages}/tags.twig (100%)
rename themes/default/{content => pages}/view.twig (93%)
I have no idea exactly what all this means, but I can guess that some feathers were moved out of the content directory and up a directory, and that content was renamed to pages. If I had just done a raw upload of the git download (like I did once before) to the server with an sftp client (I use ForkLift), I'd have screwed things up again, as I'd have many duplicates. Now I've got a semi-clean upgrade. But now I've got a new issue that I hope isn't caused by my upgrade method. Earlier it was also having some issues with an 'index' with the same name as the tag, but since I'm not getting that now, I guess it's fine.
July 06 @ 05:58 AM | 0 Comments | Tags: chyrp | TrackbackDon't just overwrite your chyrp directory, set up a 'staging' area first, especially when the guy who writes chyrp assumes everyone will use git so he writes absolutely no 'safe upgrade' instructions for people using releases, nor "files that contain your config info so these are the most important". Good thing I backed up first :-
edit: also, copy over your .htaccess at the terminal
edit: ah, good, the staging area is broken. beautiful. and the developer thinks everybody's gonna have git so they can do a git pull on their webserver. Dreamhost survey sez...
[attila]$ git
-bash: git: command not found
Chyrp doesn't come with comments by default. There's an extension, and when you install it, you get an awesome unexplained warning not on the extension details page: "Please remember to update the permission settings for each group.". What?
This means that you need to go to manage user groups and give them permission to add, edit, delete comments (there's also 'edit own/delete own' so that users can edit and delete their own comments.
Nice, the one feature I'd like to see is the ability to put in a timeframe for this, so I can say members can edit comments for 5 minutes, etc.
June 24 @ 08:40 PM | 1 Comment | Tags: chyrp, modules, comments | Trackback