Knut Sparhell

Your pages also works.

There is probably a fatal error happening very early. Could even be a syntax error in PHP.

Deactivate your plugins, one by one, and test.

It seems your permalink structure is not reflected correctly in the .htaccess file. Try resetting it to default form WordPress, then set it again to your preference. Any errors after the save?

And is everything ok while the permalink stucture is default?

It seems to be som confusion here.

This is www.remarpro.com. Your domain is not pointing here. wordprees.org is the only domain here.

It may be that you have a self hosted WordPress (ORG) blog in a multi site setup using domain mapping. If you may use phpMyAdmin you are probably self hosting. If the domain pionting to your old blog is yours, then you may have it point elsewhere. There you may set up a new WordPress (ORG) blog.

When you mention myname.wordpress.com then that blog is something completely different, a blog hosted on WordPress (COM). If if you have pointer at your wordpress.com account that points to your old blog as an addiional self hosted blog.

You alsom may have a domain that is pointing to wordpress.com (premium account).

Be specific about what you have (which domain?), and where (which hosting provider?), and what you want to do. Then you will get better help, either here or on the wordpress.com forums.

Change the name of the plugin to be globally unique. Prefix the name with your initials. A rule of plugin development: Prefix everything that is global, like name of plugin, all defined constants, all declared functions and every new global variable you introduce.

It seems this plugin uses an anonymous function as a parameter to an action hook. Anonymous functions was introduced in PHP 5.3. What is your PHP version?

Two strange things:
* Why didn’t WordPress detect that there was a fatal error when activationg this plugin? Did you upgrade an active plugin by overwriting files through FTP, or did you use the upgrade facility in WordPress?
* And after activation, the plugin itself should have deactivated itself, if the requires PHP version was not met.

Until this is resolved you have to deactgivate this plugin. Do deactivate a plugin when you cannot log in, use FTP to rename or delete the folder newsletter-sign-up from your wp-content/plugins folder.

Contact the plugin author, qoute the error message and mention your PHP version. Your PHP version may be found through your hosts admin panel or through the plugin WP Serverinfo.

No, the database engine might run on a separate server.

The name of the server is given at setup time, and resides in wp-config.php. The default server name is “localhost”, wich means “this server”. Change it to whatever server that runs a MySql instance you can access, and create your database there. This service must of course accept network access.

I have had WordPress running under IIS for many years without major problems. WordPress runs under PHP, and as long as the PHP setup is ok, then WordPress and any plugin will run. I have tried and are using hundreds of plugins, and I have never come across one that doesn’t run because of IIS.

Pretty permalinks is dependent on a rewite module on the web server. This is true for Apache and for IIS7. So there is noe real problem with permalinks.

The question on platform is a question on which platform you are familiar with, and the server provider.

I run my own servers and have no knowledge on GoDaddy.

Must add:

Ah, now I see that this new version also shows pending counts, server information and sw versions! Excellent!

A very minor thing is that you seem to regard “Not indexable” as something that calls for action. But that only is a notice. Some blogs doesn’t want to be indexed. May be this should have a brown or blue color, and may be a question mark as “icon”, if any.

I didn’t see this extra info because my clients were not updated with the new plugin version yet. And this reveals a real problem, may be not with this plugin at all, but the way WordPress checks for updates: Even when the status screen says 0 plugins to update for client that was recently “updated”, when I actually enter the site, there is a plugin update available after all. So I guess your status check doesn’t itself trigger WordPress to check for updates. Only a real blog visit does?

But if these client update request also triggered this WordPress mechanism in a way, it would be absolutely perfect.

From this day on, thanks to your plugin, I need no more visit each blog to see the number of pending posts or comments, and that’s even more important to take action on, than updating plugins or themes. As technical administrator, my role will also be to review pending content on behalf the blog owner. They sometimes fail to take proper action in reasonable time, even when warned by mail. So thanks again for the work of making and maintaining this plugin.

Nice, now I can see the Client Type(s) on the Clients listing.

After using it for over a week I think:

• Very useful!
• Need to update each client without expanding them, or an expand all button
• Need a counter bullet on the menu item too, showing the sum of all updates for the clients
• The “Right Now” thing is not important, but for completeness. And almost every custom post type plugin I have tested add their count of such posts in there

• Idea: Link the number to edit.php and the word “Clients” to the Client Status screen

@celluloidblonde: GoDaddy says:

All of our Linux hosting accounts can support PHP 5.2.14. Older accounts that had PHP 4 enabled support 4.3.11 but can be upgraded to PHP 5 at any time. For more information, see Viewing or Changing Your PHP Language Version.

If you do not switch to PHP 5 you will not be able to run WordPress 3.2 (next major version).

The right now table is a dahsboard widget, The Main Dashboard Widget, that tells you how many posts and comments you have, for instance, and with links to the overview. There are a few hooks to add rows to each column of it, dependig on if it’s posts or discussion relevant.

The Client types does not show on my Clients overview here, and I might investigate it by installing this plugin in dashboard mode of more sites.

Sorry, I have no screen option to check, just the date to uncheck (now unchecked as unneeded).

I see from data.php that things like PHP and MySQL version is being put into the XML. It will only need to extracted and displayed on the dashboard site, I guess.

Small annoyance: When updating settings there is two yellow message lines saying the settings are updated. WordPress has it’s own, and you probably add your own message, too.

Idea: Add a row to the “Right now” table, saying something like:
12 Clients need attention

This plugin really saves me a LOT of time, already.

Great plugin.

Wishes:

• Pending comments
• Pending posts
• PHP version
• MySQL version
• Server OS
• Less bright green colors (dark green)
• Better view of client statuses, see all info without having to click on each to open
• Client type column in clients table (edit.php)

Mark: Could the IIS6 canonical redirects problem be a candidate for a quick hotfix (version equals 3.1 and Server equals Microsoft-IIS/6.0), just disable canonical redirects i that case.

Same problem. I installed 3.1 RC2 on a test site, this plugin and set it to fetch “Bleeding edge nightlies”.

No matter how may times I (succesfully) upgrade to the latest, when returning to the upgrade page, it says there is a new version available.

Also manually installed wordpress-latest.zip and still, as soon as I reload the update-core.php, there is still a newer version. Can’t be right!

Server: WIMP (IIS7, PHP5.3, which runs several stable WordPress installs perfectly)