paulaeisenberg

OK, I solved my problem, and it was a dumb problem to have. I hadn’t disabled WP-DB Cache Reloaded plugin. Once I did, the problems disappeared. I tried to re-activate it, but got more errors. So I’ve trashed it until the plugin author can rewrite it.

I hope you’re right! I tried it via Safari and the app, and neither worked for me. I’m typing on the screen keyboard now, and it’s not half bad!

I should add that I was using my dashboard via the iPad Safari browser, not the iPad app. Will try the app too.

I’m able to do most of what I want to do on my new iPad (just arrived today). However, I often need to copy/paste text into the body of the new post pane, and I can’t seem to make it work. If I copy text from a web page in Safari, when I go into the text body area of a new post and press so that the Paste command appears, the copied text ends up in the title field, not the body. Even if I’ve first entered text into the title and have moved to the body and tapped, the pasted text does not go into the body.

Any tricks I’m missing?

I would love to see step-by-step instructions for making a theme natively compliant with the new custom menus creation.

I just discovered the trick, I think. See https://www.ads-software.com/support/topic/394475?replies=15#post-1527375

I just discovered something: If I click on the Dashboard button so it opens, I see Updates. Clicking on that produced:
An updated version of WordPress is available

You are using a development version of WordPress. You can update to the latest nightly build automatically or download the nightly build and install it manually:

and two options: Update automatically and Download nightly build. With some trepidation, I cliked Update automatically, which worked. I’m not at 3.0-beta2-14860. I’m not sure the plugin is necessary.

Westi, unfortunately, even though I’m using the v0.91 of your plugin, I’m not seeing the update button in Tools. All I see is the option to update the core, which would bring me back to 2.9.2. I’ve got Bleeding edge nightlies checked.

I did use the latest version of the plugin, .091, and still have the problem. I’m not seeing the Tools/upgrade option.

I’m presented only with the core update link.

There must be a bug in 3.0beta 2. I’ve got the beta test plugin installed. This is a new installation of WP 3.0beta2, no modifications yet aside from adding the plugin. Here is a screenshot of what I see:
https://gyazo.com/3d7f846a6e7918de35e28ededbccd8da.png

No Upgrade under Tools. If I were to click on “Why don’t you head on over and upgrade now,” I know I’d end up with 2.9.2.

Awarner, this is something I’m sure many of us would love to have, and it should be built-in, not require a hack or plugin, seems to me. Like you, I have many PHP and Text widgets, and most of them can’t have titles that would show on the front end. So I have to open them up one by one to find the one I need to work on. That’s a big waste of time and shouldn’t be necessary. A simple check-box like “make title invisible” should do it.

Thank you, esmi and t310s_. That’s good to know.

I’ve used WP Super Cache, WP-Cache, Hypercache and DB Cache Reloaded. All of them seem to disrupt some admin functions. Even with no cache plugin running, and even with 230 queries on our front page, the speed seems to hover around 0.9 second. So I guess that isn’t too bad. We moved from a slow host to Hostgator recently, and it’s been much faster.

Shane, thanks, but that’s not what I meant. I mean that as our site grows, the number of posts will continue to grow, and that’s a good thing. But I’m worried that at some point, the sheer volume of posts and images could overwhelm the database.

I think there is a problem with the WP repository’s version of the theme. You can get it directly from https://wordpress.bytesforall.com/?p=87 and load it via FTP in place of what you have now.

Thank you, neodan and GabeYoung. I do have a lot of plugins, and since things are running nicely with 2.9, I think I will wait for 3.0. If there are new security threats in the meantime, I’ll have to rethink that, of course.