- wp-admin write new post: tags autofill text function doesn’t work
- wp-admin write new post: “Add media:” buttons above text field absent or not working
- wp-admin custom fields at bottom of write new post: none of the custom fields can be “droped down” or reduced
- wp-admin in write new post on sidebar: publishing status open and edit button locked, can’t close “publish post” stamp.
- wp-admin in write new post categories: unable to add new categories, categorie dropdown not working, label “+add new category” absent
- wp-admin in write new post plugin: “all in one seo pack” locked, unable to open
- wp-admin in write new post: “custom fields” open and locked, unable to close
- wp-admin in design – widgets: widget tabs locked into position, unable to move them to reorder them

I guess there may be more issues, but I only tried to resolve the above list. I emptied cache and cookies but this didn’t help. I first couldn’t believe that these problems could be caused by Google Chrome, therefore didn’t try out other browsers. But after a few days of desperate intents to solve the problem I gave up, started the Internet Explorer 7, and everything but the widget reorganizing worked fine.
Then I decided to try Mozilla Firefox, to see if it would solve the issue of the “locked” sidebar widget buttons. It did. All sidebar widget objects can be draged and dropped as supposed to by the functionallity of WordPress.
One weird thing I want to add: Until one month ago I used WordPress 2.7 and all these problems didn’t exist. All this started with my upgrade to WordPress MU!!

I will use Mozilla Firefox for WordPress MU publishing from now on, just to much hazzle with Chrome!!

Incoming search terms:

• add category wordpress not working in chrome
• wordpress rss feed not working in chrome
• wordpress rss feed is not working in chrome
• wordpress custom fields working in chrome
• wordpress add media chrome problem
• temas para google chrome sobre o mu
• temas google chrome do mu
• temas da google chrome do mu
• tema google chrome mu
• tema google chrome m u

Bookmark It

Hide Sites

No related posts.

Error: I couldn’t find any feeds at spirituality.ralfengel.com [HTTP request error: Invalid protocol ""\n]. Try another URL

when I try to add the new URL to the plugin syndication feeds.

When I click on the feed url of the subdomain blog I get this message:
This page contains the following errors:

error on line 3 at column 6: XML declaration allowed only at the start of the document
Below is a rendering of the page up to the first error.

But, there is nothing else below…

I’ve used the following commands (pasted into the sidebar)

<?php bloginfo(‘rss2_url’); ?> (RSS 2.0 format)
<?php bloginfo(‘rss_url’); ?> (RSS 0.92 format)
<?php bloginfo(‘rdf_url’); ?> (RDF/RSS 1.0 format)
<?php bloginfo(‘atom_url’); ?> (Atom format)

to get my feed info shown. It shows as:

http://spirituality.ralfengel.com/feed (RSS 2.0 format)
http://spirituality.ralfengel.com/feed/rss (RSS 0.92 format)
http://spirituality.ralfengel.com/feed/rdf (RDF/RSS 1.0 format) http://spirituality.ralfengel.com/feed/atom (Atom format)

I’ve tried them by pasting each one into the browser, but neither works.
Weird is that on my first subdomain everything went fine. So I did tons of Googleing on this issue and found a plugin called “Fix rss feed” made by Fuk Loi.
This plugin will search ALL files on the server for “empty spaces” and eliminate those. I used it, had to do a lot of CHMODing, and tried to syndicate again, still without success. So I went to have a look at Feed Validator, ran my feed through their analysis and it came up OK.
My last hope was to get into my SQL management page on the host and see what was going on.
At the PHP my Admin panel I checked my tables out:

- Check Tables
- Analyze Tables
- Repair Tables
- Optimize Tables

I came back to my Syndication Plugin and It worked fine. It accepted the RSS feed URI and it did an update of the last 10 posts without any problems.

To resume, I am not able to put my finger on the exact problem of this problem, but something that I did must have fixed it.

I’d love to hear from you if this information has been of any help for you.

Incoming search terms:

• error on line 3 at column 6: xml declaration allowed only at the start of the document
• wordpress mu rss feed
• wordpress feed doesnt work
• wordpress feed mu
• wordpress mu et rss
• wordpress mu feed
• wordpress mu main blog feed url
• wordpress mu rss
• common rss feed wordpress mu
• wordpress multiuser rss

Bookmark It

Hide Sites

No related posts.

In this post I will only discuss issues not mentioned in the readme.txt file that came along with WPMU and I will add some information to certain subjects, where I found easier ways to do the job.

If you are hosted on a free server you will not be able to use WordPress MU.
Here is the list of minimum requirements for WordPress MU to work correctly on your server:

1. Backup Backup Backup
2. Apache mod-rewrite on
3. Virtual Host or CNames capability
4. chmod 777 for root directory
5. MySQL database
6. PHP 4 (5) support
7. Importing posts comment data

1. Backup Backup Backup
A dirty installation from WordPress to WordPress MU means that we do have lots of posts and comments in an existing database! Back it up!!!! Go to your MySQL control panel and download the whole thing to your machine. Further do an export within WordPress. Double security!
Keep them in a save place, you will need them to re-integrate your data into WordPress MU later on.

2. Apache
Apache must be configured so that mod_rewrite works. If you were using WordPress before on your server and you used “nice url’s” then you are good to go. If you don’t contact your host and ask them to activate mod-rewrite for you. On my server Hostloco mod-rewrite was active upon “delivery”.

3. Virtual Host or CNames
Your virtual host may not be activated, no big deal, there is a way to get to use WordPress MU on a server without virtual host. What you do need in this case is CNames. Before creating a new blog as a subdomain (e.g.: main domain here is http://ralfengel.com subdomain url to blog is http://wordpress.ralfengel.com) that does only exist virtually, no need to create this subdomain, just add a CName on your web host control panel like this: wordpress.ralfengel.com , then create your new blog in the WPMU control panel. This worked fine for me.

4. Chmod to 777
After uploading all the new WordPress MU files (WITHOUT TOUCHING THE wp-config-sample.php!!!!!!!!!!!!!!), call the index.php file on your domain in your web browser to initialize the installation. You may read a warning message on the bottom to change specific directories to chmod 777. Use FileZilla (Free FTP program) to set these permissions. If the chmod for the root directory is to be changed you may need to contact your host, since (at least in my case) FileZilla didn’t seem to be able to change the values chmod for the root directory.

If everything went right you should now be able to fill out the installation sheet, index.php with the database information needed. After saving your new – empty – blog should load in the window.

5. MySQL Database
Not much to say here, create one, create a user, and you are ready.

6. PHP
Usually the servers today are set to PHP 4 and can be set to PHP 5. My installation of WPMU works fine with PHP 4, but I did find a plugin asking for PHP 5, so I just changed it in the PHP permissions and preferences in the hosts control panel.

7. Importing posts comment data
Since I did a “dirty” installation, I have a backup.xml file on my hands, which contains all the data from my MySQL database. I used the WordPress Export function file. It was huge. 370 posts, 1200 categories, 180 comments and so on made it a pumped up 3,8 MB.
Wordpress MU may – will – can – not import this size of file using the WordPress Import function (I don’t know why, just know that it doesn’t work).
You will need a html editing program to break this file into bits, hehe!!
I used ACE HTML Freeware to do the job. It is somewhat nifty to do, especially because this is a heavy file, takes a while for it to load, and the tab switching is slow, too. You’ll need patience to do it.

Find the very first <item> entry using the – edit – find… – function.
Copy everything from the beginning until just before the <item> and paste it into a new xml file tab.
Copy this:
</item>
</channel>
</rss>
And paste it below the “header” of the file.

If your xml backup file is 4mb of size, then you will have to create 4 files, since I’ve noticed that WPMU will not import anything bigger than some 1.4MB of file size.
Use the right scroll bar button to judge more or less 4 visual divisions of the file. Cut each data segment out including <item> and </item> and paste it in your new header – footer file.
Save it and repeat this till done. My files ranged from between 900KB and 1.2MB, the latter already starting to cause trouble when importing. I had to repeat import 2-3 times for the bigger files, so try and keep the file size low, maybe that helps.

I hope everything will go well for you on this task. I did run into some trouble after having done all the above. See my Upgrade Issues Post for more.

Incoming search terms:

• enwheeling this is a wordpress mu powered site site news

Bookmark It

Hide Sites

No related posts.