nellcooper

I teach, through the local college, non-technical small businesses and nonprofits. The domain was set up way back in 2007 or 2008 and can’t be changed because too many former students still use it for their “sandboxes.” It is set to discourage search engines and isn’t a publicly promoted site. If it makes you feel any better, I probably will not be teaching any more WordPress classes after this academic year. You can commercialize it and kill with greed to your hearts content. Helping solve the problem would have been a much better use of your time and generated much better WordPress user experience and loyalty.

@zulfikar Nore: Thank you so much for your help. There was indeed a plugin conflict. Deactivating the ReOrder Posts Within Categories plugin seems to do the trick. Will look further at the plugin to see if there’s anyway these folks can use it for another of their desires while displaying all of their performers and lineups. Alas, they are of an age that can’t grasp anything except a “printed page” design, but can’t afford a “webmaster.”

Again, my thanks Mr. Nore.

According to the plugin listing, Link Manager hasn’t been updated since 3.5. Where is that functionality supported in 3.8? Anyone know?

The ability to create simple link list for the sidebars is *very* useful in many instances. I really, really miss it — especially since I’ve got a small non-profit that desperately needs the feature. Have no idea why WordPress took it out of the core program. Designing the program for web developers and IT departments vs basic users not the best direction in my opinion.

@lance Willett: Thank you for the link to the documentation. For some reason I was having no luck finding it on a search.

I do like the Featured slider/grid and the extra menu in Twenty Fourteen. Will hack a Child Theme this weekend for the color and centering issues (and possibly the narrow content column; honestly, not everyone is using their mobile phone and that’s what responsive design is for anyway.)

Many thanks for the help folks! I’ll have to hack the color scheme and center the theme content in a child theme and possibly create a new front page template, if I use it for these folks. I really like Twenty Twelve as a Parent Theme for clients on a tight budget who need something just flexible enough without a lot of customizing and maintenance. Alas, they want a feature slider but need soemthing very, very simple to manage and have already purchased a calendar plugin that is stretching their learning curve. (Of course, they’d also want blinking text if they could still have it…)

Also, I appreciate the tip about Jetpack. Will now remember to not set up Jetpack for these people. They wouldn’t really use it anyway and having another account would only confuse them (we’re still working on the concepts of domain name registrar and web hosting service versus ISP and Gmail).

Doh! Actually, I did use text-decoration. But thanks to your kind observation on my failed typing skills while multi-tasking, I discovered that I had left a space between the hyphen and “decoration.” All better now.

Thank you so much for your time and assistance. I really do appreciate all of the volunteer Team WordPress.

(I will now go back to figuring out why I can’t put a “More” link in the list of excerpts…)

Again, my sincere thanks.

A big SHOUT OUT “thank you” to Riche. You saved me a lot of time late at night when my brain was melting. Child Theme now working exactly as needed.

I’m posting an update on my previous post. I began a systematic test of the various plugins I use regular and recommend starting with Askimet.

Quick Summary of WordPress 2.8 Issue

It appears that some people are reporting problems with upgrading to WordPress 2.8, particularly with customized themes and plugins. The only problem I experienced was with the Publish options failing after upgrade on two of my WordPress-based sites on two different hosting services. By deactivating all of the plugins and reactivating them, I was able to restore full functionality to one site. On the other site, I needed to deactivate, manually upgrade all plugins requiring updates, and reactivating them one by one. Once that operation was complete, full functionality was restored.

My Troubleshooting Method
On the my primary site, which has the installation that cannot be automatically upgraded for WP or plugins, I deactivated all plugins, logged off, closed the browser and started again.

At this point the Publish box fields (status, visibility, date) began to act normally. I then began re-activating my standard plugins one by one. If the plugin needed to be upgraded, I manually upgraded the plugin before re-activation.

Askimet: After deactivating and re-activating (and having to re-enter my API key), the Publish box problems disappeared on all sites.
Contact 7:After deactivating, manually installing the upgrade and re-activating, the Publish box problems disappeared on all sites.
Feedburner Feedsmith:After deactivating, manually installing the upgrade and re-activating, the Publish box problems disappeared on all sites.
Google XML Sitemaps:After deactivating, manually installing the upgrade and re-activating, the Publish box problems disappeared on all sites.
Wordpress Database Backups:After deactivating and re-activating, the Publish box problems disappeared on all sites.
Headspace 2: After deactivating, manually installing the upgrade and re-activating, the Publish box problems disappeared on all sites.
WP-Events by Arnan de Gans:After deactivating, manually installing the upgrade and re-activating, the Publish box problems disappeared on all sites.
Bad Behavior: After deactivating, manually installing the upgrade and re-activating, the Publish box problems disappeared on all sites.

I still consider this problem a bug in WP 2.8, but it appears to be primarily a compatibility issue that is resolvable. Perhaps the WP developers should consider some kind of plugin check or deactivation for automatic upgrades. Certainly, a warning or alert notice of potential plugin problems would be in order.

I’m just glad I found a solution. I’m still looking at moving my primary site to another hosting service, however.

Thanks for the tips! It definitely is a WP 2.8 Bug as far as I’m concerned. It also seems to be tied to something about server configurations and the ability to write to the server.

I have 3 different hosting services that I use to work with WordPress with 3 different server configurations. On 2 I can automatically upgrade plugins and WP itself. On the 3rd, which requires a manual upgrade unless I set permissions to 777, none of the suggestions above has worked.

On one of these sites, there was no problem after upgrading manually or automatically (I should mention I Have 12! installations of WP on this site for use by students). Publishing functions works fine on all installations.

On the 2nd automatically upgradeable site, after automatic upgrade was complete, I could no longer change the status or publishing information until I deactivated all of the plugins. The publish did work after re-activating my plugins, however.

On the 3rd site, the one which won’t allow automatic upgrade or installation of plugins or the WP program, I’m unable to edit the status or other publishing settings once I’ve published a post. I can update a post, but I can’t change the post status, visibility or publish date.

I’m looking now at having to move my entire primary site (which is large and not entirely WP-based) to a new hosting service.

I would love to have some thoughts from WP developers on what is the problem. Or better yet a fix to this definite bug in the WP program. WP is far less valuable if it is server configuration specific (beyond the basics of Apache, MySQL & PHP and theme specific.

Again, my thanks to thatmegirl for the tips on her problems.

The problem is that you are putting the code in the wrong place. You are putting the code after the call to write the content instead of before. Try:

<?php if (have_posts()) : while (have_posts()) : the_post(); ?>
  <?php global $more; $more = 0; ?>
    <div class="post" id="post-<?php the_ID(); ?>">
	<div class="entry">
	 <?php the_content('Read the rest of this entry &raquo;'); ?>
	 </div>

Move the code for the global more before the call to the_content (‘Read the rest…

What you are doing is setting the $more variable BEFORE the WordPress Loop uses it.

What you were doing was setting the variable AFTER the WordPress Loop wrote the_content. I hope this makes sense.

I like to put my global call immediately after theif (have_posts()) line, but some folks say it works better in the entry division. That seems to produce unnecessary repeated code calls. But either way should work. Sorry I didn’t come across this post sooner.

@baal666: Unfortunately, we can’t post images in comments, but try adding a new page and then scroll down to the bottom of the Add New Page entry screen. You should see a grey band with the title “All in One SEO Pack”. Click on it to expand it and you should see a box with fields for: Title. Description, Keywords and a checkbox for “Disable on this post/page”.

If you are looking at editing a previously published page, you should see the “All in One SEO Pack” bar after the Page Revisions section.

By filling in the Title, Description and keywords fields in the All In One SEO Pack section and saving the changes, you page should have the appropriate meta headers when you View Source while looking at the page in your browser.

I hope this helps!

I thought I would offer an answer. I have run across this problem on different hosting services. I do not know what the web server problem is, but it most cases I find setting the /wp-content directory to 777 fixes the upload problem.

Here are the answers in Spanish from Babel Fish:
Pensé que ofrecería una respuesta. He funcionado a través de este problema en diversos servicios de recibimiento. No sé cuál es el problema del web server, solamente la mayoría de los casos yo encuentra la determinación del /wp-content directorio a 777 arreglos el problema de la carga por teletratamiento.

I hope this helps others who are having this problem.

This post might help you out:
https://www.ads-software.com/support/topic/118307?replies=6

I have experienced this problem on several configurations and have web development clients who also experience this problem. The “Send to Editor” button works fine for awhile and then suddenly stops. There does not seem to be any consistent set up for the problem. I’ve had reports of the problem on everything from Mac OS 10.4.11 to the latest OS X with Firefox (the last 3 revisions) and Safari (last 2 revisions), from Windows XP to Vista with IE 5 on up.

It seems to happen within 3 months of initially setting up WordPress on a site.

I have found a few of things that appear to work temporarily to clear up the issue:

1. I start by clearing the browser cache.
2. Shut down the browser and relaunch. (Often this does the trick)
3. In the user profile, unselect “Use visual editor” option.
4. Make the change from “win = top” to “win = parent” in upload.js file.

Reinstalling or upgrading files does *not* make any difference normally.

I know it is very, very difficult to debug an inconsistent problem, but this has been going on for at least two full upgrades to WordPress. It’s forcing me to look at Joomla for clients because they Freak Out whenever they have a problem with the editor.

(And yes, I do make clients donate to www.ads-software.com whenever they choose to use it. It’s the right thing to do.)