ErisDS

Where it says:

SELECT * FROM wp_rsvpCustomQuestionAnswers WHERE 1

Delete that text, and paste the code I gave you instead.

HOWEVER there is one modification you will need to make to the code, you need to add your WordPress prefix. I can see from what you pasted that you are using the default prefix which is “wp_”

Therefore the code you need to run is:

ALTER TABLE wp_rsvpCustomQuestions ADD permissionLevel ENUM( ‘public’, ‘private’ ) NOT NULL DEFAULT ‘public’;

Hope this helps,

Eris

Hi,

The instructions above are talking about the database table, not anything inside of the WordPress admin.
What you need to do is add a field called permissionLevel to the table called “_rsvpCustomQuestions”
It is very hard to post detailed instructions without knowing a bit more about your server setup, but the basics are:
Login to your hosts control panel
Find the tool for modifying your MySQL database (probably phpMyAdmin) and navigate through it to find _rsvpCustomQuestions. Check that the permissionLevel field doesn’t exist at the moment.
Then run the following via SQL to update the table:

ALTER TABLE _rsvpCustomQuestions ADD permissionLevel ENUM( ‘public’, ‘private’ ) NOT NULL DEFAULT ‘public’;

I’m afraid if you’ve not done something like this before, these instructions still won’t make a great deal of help. If you can provide more info – do you have phpMyAdmin etc then perhaps we can be more helpful.

Eris

I am having this problem too… about to try this fix.

I have also experienced this issue, anyone got any suggestions for a work around?

Originally when I was going through the steps and my DB was what *broke* it, I was looking at the defaults to HTML editor with no menu what-so-ever issue.

Now I’m looking at the underlying issue which is that WordPress doesn’t seem to be respecting the default-to-last-setup, instead it always defaults to the Visual Editor with the kitchen sink closed.

I replicated this issue on 3 installs:

1. Completely fresh WP 3.0 install, no plugins, no data, nothing.
2. Different WP site that’s been running a while, upgraded to WP 3.0 recently
3. My main blog that is where I noticed it – a WordPress blog that has been consistently upgraded everys table release since it started over a year ago.

They are all on one server.

I then looked at another WP install on a different hosting platform. This does what you would expect – if you save with the kitchen sink open it stays open, if you save on the HTML tab it stays on the HTML tab with the quicktags menu open.

Therefore, although a setting in my database was exacerbating the issue, the underlying issue is something else.

I’d really appreciate someone pointing me in the right direction with this. I don’t have enough knowledge of servers/linux to even have a clue what kind of thing to be looking for.

When you deactivate your plugins, try WP Super Cache first ??

What version of WordPress are you using, and are you using any heavy plugins like caching?

define(‘WP_DEBUG’, true);
define(‘SCRIPT_DEBUG’, true);
define(‘CONCATENATE_SCRIPTS’, false);

@ini_set(‘log_errors’,’On’);
@ini_set(‘display_errors’,’On’);
@ini_set(‘error_log’, ###);

Not. A. Peep. :/

Hmmmmm!

It does it on 3 totally separate installs I have of WordPress 3.0 on 3 separate accounts of my reseller hosting.

It does not do it on another install of WordPress which I have on different hosting.

So it looks a server issue, which generally means I’m stumped. Anyone got any idea where abouts to go poking around in the code to find the relevant parts and/or what possible server related thing could cause this?

Thanks,

Eris

Yeah I dropped that and the related time field.

They were recreated and what is happening is what I described above. It now ALWAYS defaults to the visual editor with no kitchen sink. If I save a post with the html editor on, or on the visual editor with the kitchen sink it still defaults back to visual.

This is less annoying for me than it always defaulting to html with no quicktags, but yes there is definitely still an underlying problem.

I guess I’m back to square one! Start debugging from WP 3.0 vanilla again until I find the root cause!

I have found the culprit.

It is the table wp_usermeta, and the specific entry is wperis_user-settings.

On my blog it is set to: m0=o&m1=o&m2=o&m3=o&m4=o&m5=o&m6=o&m7=c&m8=c&editor=html&m9=o&align=left&hidetb=1&m10=o&imgsize=full&urlbutton=urlfile

Removing &editor=html gets rid of the problem of no menu. However, it never defaults to HTML even if I save a post whilst on the HTML screen – it now always flips back to the visual editor. This isn’t so bad though because at least I always have a menu open. (Although it’ll get annoying if I’m writing “codey” blog articles.

So far I have:

Installed a fresh copy of WordPress 3.0 in a separate account on the same server. – Is OK.
Copied my theme to the fresh copy. – Is OK.
Used WP export & import to copy my content. – Is OK.
Uploaded & activated (but not configured) all my plugins. – Is OK.
Copied across my whole DB. – Is BROKE.
Replaces wp_options table with the wp_options from the fresh install (which I exported before copying my old DB in). – Is still BROKE.

Therefore: It is not my theme. It is my database. It is not my options table.

*Off to continue hunting…

Used my blog on many browsers & different computers and it doesn’t work on any (just double checked).

I also just installed Twenty10 and tried that, still no joy.

As for the defaulting, that’s what I thought it did, but on my site it always defaults back to HTML, every refresh, save, save and reopen, anything it always defaults to HTML and no quicklinks menu.

Maybe that’s a clue.

I’m going to try reuploading WP 3.0 files and then I’ll try setting up my blog elsewhere step by step see what point (if any) it breaks.

Hi Esmi,

That hasn’t solved the problem :/
How does WordPress decide whether to default you to Visual or HTML? Perhaps there’s a way to reset it, or force it, or anything to get me a menu without clicking!

Eris ??