Thread

Hi,

I’m not sure what I’m doing wrong but I go to add a default HTML button (eg h6),

It shows up in the Button Definition list, but doesn’t display in the Formatting buttons toolbar in the publish page…?

If I add it from ‘My Account’ it shows up. I’m looking to set the defaults so this isn’t preferred.

Thanks,
Neo

Hi Neo,

Does the Formatting Button bar show up at all on the Publish page? Adding a new default button at Admin > Content Administration > Default HTML Buttons should immediately update the button list in your account. Does that not happen?

Which version and build are you using?

Cheers

Greg

Hi Greg,

I’m on Version 2.1 Build:  20100810

The toolbar does show up in the Publish page, just not as specified in the Default

This is what I’ve found since:

* Setting the defaults gets the correct buttons to display on other profiles (but mine).

* It looks like the settings from ‘My Account’ override the default setting and so appears more like a profile issue

Neo Mudaly,

It looks like the settings from ‘My Account’ override the default setting and so appears more like a profile issue

This is correct. The Default options you were amending are the default which will show in your account area for new members. They have no affect what shows on Publish page.

You need to update your HTML buttons in your Account preferences. These will show on your publish page.

Does that help?

Thanks for confirming John,

Is there an option to disable the ‘My Account-add-HTML-buttons’ option?

Once I set the default, I want to avoid members tinkering with the format in which content is added.

Cheers,
Neo

Hi Neo Mudaly,

There is no preference to do this though you could certainly remove the link from the appropriate theme in themes/cp_themes.

cheers, thanks Brandon

Please explain fully for those of us who are trying to learn how to use 2.1 to publish.

I went to the default html pref section after much searching and with a little help from previous posts on this board. Not even sure how I got there. I see that the html buttons are there, or a few are anyway. I submitted them again, but they don’t show up on the publish page. I am the super admin and the user. So buttons for blockquotes, bold, links, ital, etc. don’t show. Buttons for upload, glossary, do.

How do I turn the buttons on in my blog’s publish page. I was in the preferences page for the blog. It seems to me that that this is a basic function that should be fully explained in the documentation. But when you search for “formatting” you get a bunch of programming notes that do the user no good. I’m amazed that given the competition for WordPress, you guys haven’t figured out the importance of a user friendly product that small businesses can managed without the help of consultants.

Anyway, your support always is good when I ask a question, and I need help on this one, please. Yes, we’re going to ad Wigwam (sp?), but my consultant is in the hospital and won’t be able to help for awhile, I don’t want to bother her.

It looks like the format buttons have higher priority on the individual members account.

So once you set the default buttons (Admin > Content Admin > Default HTML Buttons), they will show up as per your setting for new users only.

So you’ll need to tweak the buttons on your user account. Use the sidebar and click “Control Panel” under “My Account”. You’ll find “HTML Formatting Buttons” in the left nav of your control panel.

Formatting buttons need to be enabled in the Custom Field settings as well as in the Channel Preferencess under “Publish Page” customization.

Let me know if you need further help 😉

Don, when you import from 1.x to 2.x, Show Formatting Buttons isn’t turned on by default. I went ahead and changed them for you for the main parts of the site.

Does that help?

I’ve spent a better part of a week trying to figure out what was going on with this, thinking it was a problem on the SAEF side of things, only to discover it was a setting on the EE side of things. Is there a set of instruction somewhere that included this as something you need to do as part of the migration to 2.x?

Not that I know. There are update notes for EE 2, but this obviously didn’t warrant inclusion. It’s working as expected now, I understand?