ThaiClimate

Thank you for steering me further to the built-in functionality. Clearly user error and ignorance sent me to the plugin a bit hastily—at least relative to achieving the above. Slightly related, I have noticed that the plugin does offer the ability to implement column-reverse for mobile stacking of text/media blocks. That does not yet appear to be built-in, but not much css, if one wishes to go without the plugin.

I achieved my objective by abandoning the Featured Images approach. I installed the twentig plugin and used their Full Screen Cover Image block to deliver the design element I was looking for. Thank you to those developers.

Thanks again Andrea,

See all the subsite meta data populated in the appropriate subsite option’s folder now. Should have thought to look there. With that I can now go back to nailing down getting vhosts and .htaccess playing together so I might actually be able to display one of these subsites.

Thanks Andrea,

Han indeed seen your tutorials site, and lots of others. You must be pretty tired of users like me, especially when typing things like site_meta instead of _sitemeta. Also saw the discourse on terminology changes so should have been more careful there as well. Anyhow, if someone is interested would just like to know the following?

1) A subdirectory under blogs.dir should be automatically created for each site. (Now when I upload media to the main site via “Add New” in “Posts” it gets stored in the old Uploads/yr/mo folder.

2) Should not _sitemeta data be populated for the any new site when the site is created? All the site’s new tables are created but that table is not populated?

Thanks

Thanks again. Back at it with little change.

First off. Very newbie question for WP multi sites. When a new site is created by Super Admin, does WP automatically create the directory in blogs.dir for that site [#]? If not, is there any other physical representation of the site that can be seen in the file structure/the new site(subsite’s) actual folder following the site’s creation. I ask because I’m not seeing anything in the blogs.dir folder, but am not getting any kind of error that the directory could not be created? If all content goes into blogs.dir/[#] and themes are all in themes, trust WP proper does nothing with the site’s physical path folder?

Probably more critical the _site_meta table shows nothing for any subsites. Meta data only for site[1]. The _bolg table has all sites though. Guess I should have checked this out earlier, but certainly going to be a problem with no theme info to help serve the page. But surprised I’m not getting any errors? This is a whole other basket of issues I trust.

Regarding the directive: DocumentRoot “/Users/username/Sites/mainsite”, etc.
I do not have a folder names mainsite. So ../Sites/ itself is the folder for mainsite’s content. All files are in the Sites/ root, e.g. …/Sites/wp-config.php, etc.. So unclear on where such a directive would be pointing?

Thanks much for the suggestions so far. The hosts file had been updated, else I would never have gotten mainsite.dev to feed me the WP’s mainsite content. But I had not done any mapping of the subsites as suggested. So took care of the subsites in hosts and vhosts.conf. Unfortunately, the situation remains unchanged. WP only serves up mainsite.dev, with just the directory listings for the subsites, which are physically empty.

One thing I did notice in keesiemijer’s settings’ suggestions above, is that it has mainsite as a subdirectory in Sites. I’ve got everything at the Site’s root, figuring that might be less prone to error. Will try moving everything one level down and see if that triggers any changes?

As noted earlier, I went this rout as the MAMP solutions above were not working for me (have used Single User WP on MAMP successfully for years). Figured I would give the native Snow Leopard package a try–again noting that it’s a bit harder to get the Apache/Php/Mysql thing set up than with MAMP. But once up, figured I would be no worse off. And indeed, I’m visibly further along, as with MAMP I could not get the mapping to even serve me WP’s on main site for installation. Also, if this could work, be another set of options for folks. But close is not close enough, so maybe I will need to go back and try again with my MAMP configurations.

Ok everything has been reinstalled under the fake domain mainsite.dev. Thus we have mainsiste.dev/subsite1, mainsite.dev/subsite2, etc. This is how the urls appear, but the subsites have the same problem as before, WP pages are not being served to them. I just get directory listings for subsites.

Here’s the user.conf code

<Directory "/Users/username/Sites/">
    Options Indexes MultiViews
    AllowOverride All
    Order allow,deny
    Allow from all
</Directory>

Here’s the vhosts.conf code

NameVirtualHost *:80

<VirtualHost *:80>
  <Directory /Users/username/Sites>
    AllowOverride All
    Options +FollowSymLinks
  </Directory>
  DocumentRoot /Users/olmini/Sites
  ServerName mainsite.dev
</VirtualHost>

If “Options +FollowSymLinks” is not there, error 403 shows up?

Do you mean assign the fake to the main site root as in mainsite.dev. When I do that I get the “Forbidden” permissions error?

vhosts.conf settings:

<VirtualHost *:80>
  <Directory /Users/username/Sites>
    AllowOverride All
  </Directory>
  DocumentRoot /Users/username/Sites
  ServerName mainsite.dev
</VirtualHost>

FYI, I don’t get the error if I assign a fake to a WP subsite/subdirectory. In fact it seems every time I try to assign a fake domain to a WP install directory I get the “Forbidden” error.

Ok, just reinstalled and network settings are now working, but WP pages are not being served to the subdirectories/sub-sites. I’ve posted a question about this at another topic.

A slight change in direction. Been using MAMP for several years just fine, but could not get the above to work. Decided to see if I would have better luck with Snow Leopard’s own Apache 2 install recognizing it’s a bit more cumbersome to get going. Well I’ve got WP Network Sites functioning, but WP files are not being served to the subdirectory sites. I just get directory listings when at the the sub-site/subdirectory roots. If I append a specific wp-admin file path to the sub-site’s url I get a 404 error.

My .htaccess file is per the code generated by the WP network install script. WP is installed in Snow Leopard’s User Sites root folder …/user/Sites/ with the root url being https://10.0.1.5/~user/ I’m not using any virtual hosts at the moment so the urls are straight out of Snow Leopard’s box. The urls all seem to be appropriately represented in the config.php, .htaccess and within WP sub-site configurations.

Is there something specific I might try with the PHP’s httpd.conf and httpd-vhost.conf settings? I have tried the following in the vhost.conf:

<Directory "/Users/username/Sites/">
Options Indexes MultiViews
AllowOverride All
Allow from all
</Directory>

But this just gets the the “Forbidden” permissions’ error for everything including the main site.

Actually thought I’d commented out the wp-config.php line enabling network settings, but had not. So message is gone and replaced by nothing. No network, Super Admin. Back to the original Dashboard. Database was updated with 6 new tables, nothing added to the Dashboard. No other warnings, just the old single site set-up with more tables.

I’ve checked everything at this topic already.

I’m getting the same message attempting to install it locally for testing purposes using subdirectories.

Thanks much Rok.

Actually, the problem turned out to be the simple but elusive wo_head declaration not being called from the header.php. Anyone else having this problem or a general lack of css from plugins not displaying properly, make sure you’ve got:

<?php wp_head(); ?>

between your <head>…</head> tags in your header file.

Well it seems I’m back in the permalink dungeon. The only way I could get page navigation to work again was to resort to the default permalinks. I’ve tried all the tricks regarding removing, rewriting the .htaccess file, but still the same problem. It’s ugly urls until this is fixed I guess.

Any updates out there on the permalink page navigation issue. It was working in 2.2 no problem, but not 2.3. Will check the host’s forum to see if any help there as well.

Actually, the plugin above does not duplicate a post–ie create a duplicate database entry with the same content but different id number. The plugin creates a template from your post. While useful, it won’t help me much as I would have to create all kinds of templates for every page I wanted to duplicate. Nearly every post I have gets duplicated in another language, it would be nice to not have to recode for any graphics and/or extra html.

Any plugins out there that will just tell the database to create a new post, with all the data from the one you’ve selected?