PostNuke

Flexible Content Management System

News

Share your tips

Contributed by Anonymous on Aug 11, 2001 - 12:40 AM




Well I, like several others am exactly in that situation as I merely untarr'd the system as is, putting everything in /html.













My solution was to telnet in, and from the command prompt, globally replace/modify my files as stated in the README_FIRST file.













  1. First and Foremost, BACKUP YOUR themes in case you shoot yourself in the foot. So, from the parent to /html:

    tar -zcvf themeback.tar.gz html/themes/







  2. Then comes the fun. Now mind you, what I'm about to show you can and will shoot you in the foot, your brother in the foot and your mamma as well. If you're unsure, then don't do it.

    Warning aside, piping the results of find into xarg I used perl to perform a file-wide search and replace using regular expressions. So here we go (and don't let the word-wrap fool you, this is all one line):

    find ./html/themes -name "*.css" | xargs perl -pi -e 's/(url()(/themes)/$1/html$2/gi';







  3. Now go check your work. If you managed to cripple your themes, then restore the backup via:

    tar -zxvf themeback.tar.gz html/themes/














    Now I know what you're saying, hey, I'm not in "/html" ... I'm in "/BOBnLARRY" ... okay ... the stuff you want to change is right before that $2 .... so it looks like this:








    find ./html/themes -name "*.css" | xargs perl -pi -e 's/(url()(/themes)/$1/BOBnLARRY$2/gi';







    (again, don't let the word-wrap fool you, this is all one line)













    So now I've shown you mine, let's see yours !

1040