Steve Ryan

For those effected by this error, hopefully this helps. Replace line 223 in easy-columns.php with the following:

<?php if($this->options['use_custom'] || !empty($this->options['custom_css'])){ ?>

I’m submitting a patch to the author immediately following this post. ??

Hmm. Going to ignore the assumption that I don’t understand the plugin or its purpose. Assumptions make us both look bad…

I have some screen shots for you to look at that can help illustrate the first problem outlined above. Like I said, it was resolved completely by altering a data point in the new row created in wp_sites table, so I think that’s just an error in the plugin code someplace.

And as for my other points, perhaps I’ll try to ask the question a different way: Does the new network admin page resolve to a different URL than the first one?

For example: Let’s assume that we have a network which has a base URL of mysite.com. The URL mysite.com/wp-admin/network will lead you to the network admin page for the primary network created.

Now, using your plugin, I created a second network using the domain myothersite.com. I can see the actual site when I use the link in the top nav bar. (It’s listed along with the other sites on the first network).

What is the URL that is created for the new network admin panel? I haven’t been able to find the link your documentation refers to, and the logical choice of myothersite.com/wp-admin/network redirects back to the primary site network page at mysite.com/wp-admin/network.

Thanks for your assistance. If I can get your email address, I’ll forward you the screen captures of the “second backslash” problem I was also asking you about.

Was just looking for the same thing. Was considering attempting to add the type to the Custom Meta Box field Type of Norcross/Atchison/Erickson fame found at https://github.com/jaredatch/Custom-Metaboxes-and-Fields-for-WordPress.

… but then discovered that my other favorite metabox class already had the type defined in there. The author’s name is Tran Anh and the page to refer to is located at https://www.deluxeblogtips.com/meta-box . The demo on the page shows a picture of what the color picker would look like.

Guys, thanks for your help with this.

I understand that the root directory for the other site would be /public_html/other-wordpress/ and like I said, the install is working fine. If I wanted that site’s URL to be

https://initial-domain.com/folder-name

…everything would be working as it should. However, the moment I try to follow the instructions within the Codex to change the site URL to its own domain, every page except the home page results in a 500 error, Page Not Found. I also observed that the General Settings page also provided me the code to change my .htaccess manually, since WP couldn’t change it when I tried to update the permalinks. (I tried changing the permissions of both the .htacces file in the directory and in the root to 777 and it didn’t help.)

Gotta end with the obvious: there’s a glaring warning on that Codex page that says that the technique described wouldn’t work with a network enabled. It didn’t specify why, and it sounded like it was a warning that WP Networks were intended to be hosted within a root of a WP install, and not a sub folder. Wondering if that has anything to do with the problem, but the directory install is a single instance of WP only (not a network of sites).

Thanks,
Steve

The article I am referring to is Giving WordPress its Own Directory

Steps 4 and 5 say the following:

4. Copy (NOT MOVE!) the index.php and .htaccess files from the WordPress directory into the root directory of your site (Blog address).

5. Open your root directory’s index.php file in a text editor
Change the following and save the file. Change the line that says:
require(‘./wp-blog-header.php’); to the following, using your directory name for the WordPress core files: require(‘./wordpress/wp-blog-header.php’);

Thanks for your help.

Uhm, thanks, but that’s not really what I was asking about.

I have the domain set up as an add on domain, and the install of the second WordPress site completed. My question was concerning the step in the install process in which you move your .htaccess file to the root directory. Once I move the file into the root, it’ll overwrite the existing .htaccess file which allows the initial WordPress network to function properly.

Is there a way in which I could combine both sets of instructions into one file?

I have the same concern for the index.php file, although I am guessing that if I used both include statements in the file, it would work OK.

Anyone else ever try to set up WP this way?

Excellent. I’m sure I’ll be able to alter the RSS page template for my own purposes. And, great to know that the post format feature is available with a regular WP_Query. Opens up a lot of new possibilities!

Thanks for your help,
Steve Ryan

Yeah, figured that out shortly after posting my question. Bummer…

I’ll look for another solution and eagerly await the feature to be added? (Please?? ?? )

SPR

Ljg3,

What an easy fix. ?? Works perfectly now. Thank you so much for the info!

For future reference, how do you know when the jQuery UI is going to need to be updated again? Is there a site that I can subscribe to that will let me know when the next UI is released? ??

SPR

Just discovered the plugin. I hope that the authors get it fixed for 3.1 soon… seems to be the solution that I was hoping for.

Totally willing to PayPal one of the developers a six pack (beer, Red Bull, soda… your choice) if this will help speed things along? ??

Thanks,
Steve Ryan