pippog

FreeBSD rocks – no zillion flavors but solid performance, easy installation of ports/packages, simple updates of ports – use portsnap – also great support if you should have any problems…

Thanks again jdembowski – great help
While I have your attention, are you saying that I basically need just other databases for the vhosts – When you say do another installation, does that mean only the database? I’m a little confused on this…

want to create a new vhost and get the working with a new database using the five minute install.

What do I do with wordpress, do I have to do another directory under the main data directory on the server? Can’t I use the one already set up. I’ll try playing with it to see…

My question was only for the posts here in this forum…

Are you saying that I need a new database for another vhost?
I already have a couple set up… what I don’t understand is how do I set up wordpress for the other vhosts – without having to reinstall wordpress for each new/old vhost? Seems silly to be installing the same program over and over – kind of clutters up the HDD.

BTW, how do you do the grey blocks in the posts?

ok, this is strange… I am able to login… like this:
https://wordpress/wp-login.php (WHAT HAPPENED – was it the permissions? Why can’t I have them the way I want them… I set the permissions to 766 so I can access and edite the files from another mache and upload when needed – I want rean & write permissions :-))
Ok, once in the address shown in the URI bar at top of Firefox3 is:
https://my_server/wordpress/wp-admin

The link at the top left is to https://wordpress/

So, what happens if I visit the wordpress vsite? I’ll try & let’s see…
Allright, it now says big_blog – start editiing.. etc.
But what do I edit? the index.php file? For I must set up the site with pages & info etc…
I guess I’ll start with their instuction thingies.. ??

Ok, now what if I want to edit one of the other vhosts?
How does one do that?

is that a typo? apache33 ? AFAIK there is no such beastie as apache33 ??
I did the goof (both finds – the d and the f and they apparently executed ok.
But the d option changed nothing… where the permissions were 766, they were not changed to 755 whereas the f option changed the permissions to 644 on the files … duh, ok, I understand… this changed the directories to 755 and the files to 644… ok,

For ClaytonJames
It was a manual install – pretty much following the 5 minute thingie – but, as this is over a period of a couple of days, I don’t recall the specifics – but after the first install Which was a total disaster… I untared the downloaded file and then erased all the installed files from the …/wordpress vhost directory and moved the files from the install-directory (…/etc/wordpress) to the vhost dir. Here, is where it all went awry… I think I was not able to access the files from the vhost directory but from the data_directory/wordpress/wp-admin/wp-install.php
I think I’ll wait a little and see what jdembowski has in mind and then I will erase and redo it one last time.
As for missing files? The files are there; I changed the permissions to comply with what was partially working but that did not change anything…
What I find strange is the entry in the error is “(include_path=’.:/usr/local/share/pear’)” I rummaged in the files to see what was being done but couldn’t find anything that I could understand – and nothing that indicated a reference to pear (that file is extant as indicated)

I was able to login to the admin page once and found that the link in the upper left corner (as specified in the instructions) did not work… and I was getting errors saying you don’t have permission to access this file – I think that was to the install or more likely the login.php file

You don’t have to worry about installing and reinstalling, I think, since you don’t have the Microsoft registry garbage to deal with when you uninstall directories & files.
I do wonder though about the instruction about moving the files from the installation directory to the site directory and leaving the installation directory empty… what’s the purpose of that? It doesn’t make sense.

Start with the basics. What’s the config for your vhost? Using the simplest php script <?php phpinfo(); ?>

Does that work from the vhost’s directory where you want to put one of your installations? What is the vhost/apache config have for the Overide statement? Are you getting anything in error_log or the vhosts error_log? Is WordPress tossing errors via the browser?

apache22 configuration is quite correct and is correct even for the wordpress vsite… info.php works from the wordpress vsite as it does from all other sites and the main directory… and the Override allows all…

https://wordpress/wp-login.php spews:
Warning: require(/usr/local/www/apache22/data/wordpress/wp-includes/compat.php) [function.require]: failed to open stream: Permission denied in /usr/local/www/apache22/data/wordpress/wp-settings.php on line 238

Fatal error: require() [function.require]: Failed opening required ‘/usr/local/www/apache22/data/wordpress/wp-includes/compat.php’ (include_path=’.:/usr/local/share/pear’) in /usr/local/www/apache22/data/wordpress/wp-settings.php on line 238

permissions for all of wordpress are set at 0766 owner is nobody whereas the other sites are owned by root and there I have no problems

I don’t bother with security issues as I do not open the server to outside cosmic forces

I suspect that WordPress is making presumptuous assumptions and thus messing up my installations…

Here are some questions that I would like to pose:
How does one use WordPress on several sites without installing wordpress on every one?

“Giving WordPress Its Own Directory While Leaving Your Blog in the Root Directory” is not clear about the root directory – does this mean the root directory of the vhost site or the server site?
My server would be https://my_server (which is also the default server root); then there are the vhost sites https://name_of_site1 ; https://name_of_site2 ; and https://wordpress (which I will change to something else). For the moment, the wordpress site is also the site for wordpress; I can leave it there and create another vhost site if needed. But for now, WordPress just plain “ain’t workin”

There are very, very vague instructions about installation… such as the passwords for security – there is no indication what the password phrases are for – to secure what? a password? which one? What if I don’t change the secret phrases for security? What if I don’t care to use the security stuff?

And I still think we don’t need lame ducks that can only suggest obvious “solutions” like pay someone else to do your work. I am not that stupid – I just think these lame ducks don’t have a brain of their own as you can see from their presumptuous comments – probably doesn’t even understand what that means.

jdembowski, I appreciate your comments; I see that you do wish to help.
??

Sorry, figaro, but that’s a lot of crap…
My local server works quite well and I have been doing development on it for quite a few years… I have no problems setting up FreeBSD, cups, samba, pgsql, php, etc. you name it… Yes, there are problems sometimes, but that is when the programming greasemonkeys decide to make great changes in their “engines” and everything has to be changed and you’re back to square one and have to relearn everyting again… ridiculous… but you can find the answers most of the time… and sometimes with the help of a few great people who have commiserated with your problem…

What a dumb thing to say, about hosted servers and mine… the reason my hosted ones work is because I tested on mine before goin “on air”

I you had an business even to post, you should have thought about what the problem might be and how it could be resolved – even asked about greater detail as to what the issues are? Obviously, you have nothing to contribute, so just zip it!

Frankly, I agree with you. I’m having the same problems, some slightly self-inflicted, but that was because it would not work as advertised and I had to try to patch things and that just does not work…

Unfortunately all these “geeks” or is it “programmers” are pretty full of shitl… they forget that there are those of us who want to use the program and are willing to put some effort in working with these “open source” things… but they always seem to think that you know as much as they do and will just zip thing through without a hitch. Well, we shouldn’t forget that these “computer tecchies” are nothing more than greasemonkeys of yesteryear…

Now, as to the installation of this stuff, I think there is a problem with their permissions and file ownerships… I’ve been trying to install WordPress on my local FreeBSD 7.0 server to see if I could use it to set up a couple of small sites… but before I put it on a commercial server (piad hosting) I want to know if I can set it up on my local server…

I found that if I set it up the way they say, something just doesn’t tick…

I took a look at some of the stupidity that was being banged around on one of your posts – a lot of hot air and no sensible suggestions…
typical ignoramuses – they had nothing to offer except – “it worked for me… I don’t see why you’re having such problems…” type of thing and throwing our some ridiculous comment about permissions and erasing files… and, or course, they had their host set it up and then it was easy… and one somebody said you shouldl spend a few hours reading the docs and studying — if you have to do that, why bother? Their 5 minutes setup is supposed to work… but of course there is no indication about how the thing should be implemented…

It makes me feel better to rant a bit too… keeps one from getting ulcers and makes one laugh in the end… and after all, there is no better medicine than laughter.

It looks more and more like a biiig mistake…
I reinstalled WordPress – BTW “WordPress is set up under virtualHost…” means that I “have actually installed wordpress.”
I’m afraid I don’t recall what specific url I used to get to install.php – but it was probably https://wordpress/wp-admin/install.php – notice that It is installed as a local intranet site under apache22 … httpd-vhosts.conf
The problems I have been facing are permissions and I don’t like it a bit that I havee to change permissions from root to nobody to make anything appear to work…
At any rate, I suppose I don’t need to pursue a further question (How can I use WordPress to set up 2 or three different sites on the same server without having to install multiple instances of WordPress?) since it doesn’t seem possible to install it even once. And I notice that there is someone else who has been driven “up the wall” with similar, if not the same, problems I am having… and he’d given up some 3 years ago already…
How can I even think of using this thing on a hosted (paid) server if it doesn’t work on my local server? ??