sleeplessindc

I tried the automatic update for rc1. It said it was installed successfully but failed to activate because of a fatal error.

It seems to be activated though when I look at the plugins list but not sure if it will be working well.

Does anyone know how to hide the settings tab on the dashboard for users who are not administrators?

Read the information at https://www.wpbeginner.com/wp-tutorials/11-vital-tips-and-hacks-to-protect-your-wordpress-admin-area/ on how to protect your site. Do tip # 7 and 6 or 5 as soon as possible. Be sure you are using the latest version of WordPress and all the plugins. I notice you have WordPress.com Stats Track in your plugins. Not sure if that works on www.remarpro.com blogs.

ntheroad,

Read the information at https://www.wpbeginner.com/wp-tutorials/11-vital-tips-and-hacks-to-protect-your-wordpress-admin-area/ and be sure to do tip number 7 right away. Use htaccess to protect the wp-admin directory to allow only your IP address and deny others (tip # 6) if you are the only author. Use tip # 5 if there are additional authors on your blog.

Discovered the solution. I had been using the Simple Tags plugin but when I activated it, I got a message saying it won’t work with WordPress 2.9, so I deactivated. That left me with no Tag Cloud. I went to Appearance/Widgets and moved the default Tag Cloud into the slot where the Simple Tags cloud had been. That fixed the fatal error and the rest of my plugins now work.

I liked the Simple Tags plugin because you can configure the Tag Cloud for font size, color, number of tags, order, etc. I checked the plugin page for Simple Tags to see if there was an update or plan to update it and found this post below the ratings box “Simple Tags can’t work with WordPress 2.9 RC”. The plugin has a WP version checker hardcoded into it and a modification is needed to that line. Once done, Simple Tags works again and I am able to use it instead of the default plugin.

All is well with WordPress 2.9 now.

I had to do the same thing. It would be nice if we could have named widgets with the accessibility mode on. I don’t understand why they can’t be named in that mode. It certainly makes them less accessible.

My error message has also changed to line 183. Maybe this means they are working on fixing it.

4seoblogs, thank you SO much! I’ve been looking for a solution for how to use password protection on the wp-admin directory and your code above solved it. This should be added to the WordPress documentation.

Yes, and what did the hosting company figure out? What had to be done to fix the problem?

I’m having the same problem. What was the solution?

The link above now gives a 404 Not Found. I’d like to know how I can protect the wp-admin directory from unwanted users but still allow my blog authors, editors, and contributors to log on.

For some reason the code above omitted the closing
and so forth.
</ul>

In your pages, you just need
<?php get_sidebar(); ?>

Then in your sidebar.php file, call each sidebar like this:
<ul class=”sidebar_list”>
<?php if (!function_exists(‘dynamic_sidebar’) || !dynamic_sidebar(main)) : ?>

<?php endif; ?>

<?php if (!function_exists(‘dynamic_sidebar’) || !dynamic_sidebar(events)) : ?>

<li class=”widget”>
<?php ec3_get_calendar(); ?>

<li class=”widget”>Events
<?php ec3_get_events(5); ?>

<?php endif; ?>

<?php if (!function_exists(‘dynamic_sidebar’) || !dynamic_sidebar(mission)) : ?>

<?php endif; ?>

and so forth.

That happens to me frequently in the site and in the admin pages using Firefox 3.5+. It’s as if WordPress lost the CSS for the page. Clearing cache and history doesn’t help. The only thing that does help is to close the browser down then open it back up.

I’ve been having the same problem with form mail on a Dreamhost account. I’ve been trying to track down why for several days and I think I’ve found the solution. It isn’t an ISP problem, it is a change/fix in WordPress. In earlier versions of WordPress, the General Settings required your e-mail address with your name. No matter how I typed it in, it would reformat it as me@mydomainMyName. My error logs showed that mail was being sent to that address but because MyName was tacked on to the domain name, it was treated as in invalid address, naturally. As an experiment, I tried removing the MyName part again and this time it stuck so just my e-mail address is there. I am now receiving all my form mail! Be sure to check any plugins you have that used the old form of the admin address and delete the MyName part.