Thread

Running EE 2.3.1 and the formatting buttons aren’t showing up in my Safecracker SAEF.

The settings in channel fields and publish page customization are set properly. The formatting CSS is accessible.

I am at a loss.

Jim, can you try updating?  I’m not able to replicate on the latest build.  I did find this bug report, which sounds like what you’re running into and which should have been fixed in 2.3.1, but I’m still thinking it may be a version issue.

That- or try the code shown in the bug- that’s how I tested trying to replicate.  Using that code, the buttons show up and work fine for me.  Do they for you?  If that works and your template doesn’t- try pasting back the template code you’re using.  It’s possible there’s something unique that’s causing the issue.

After making the posting I stumbled upon a mention somewhere that the formatting buttons only show up when placed within a custom_fields loop? Is this true? If so it will be a problem for me as I manually create my entry forms as I use different forms for different purposes. 

Please advise.

Hi Jim,

My testing bears out your experience. It seems that the formatting buttons are only available inside the {custom_fields} loop.

If having the buttons available outside the loop is something you would like to see in ExpressionEngine, I invite you to make a Feature Request!

Cheers,

OK, I supplied some bad information in my last post. Since it’s been a while, I forgot that I had moved things into a custom_fields loop.

Because of a directory name conflict, I pull the css in with the following tag:

<link type='text/css' rel='stylesheet' media='all' href='http://example.com/css/ee_saef.css'>

I have the following in my template:

{exp:safecracker channel="mychannel" return="mychannel/submission_thanks" datepicker="no" show_fields="body" include_jquery="no" status="Pending" sticky_entry="no" allow_comments="yes"}
<b>Submission Date</b>
{entry_date}

<input type="hidden" name="site_id" value="1" />

{if no_results}
No Results
{/if}
</td>

<tr>
<td>
{custom_fields}
{field_instructions}
{formatting_buttons}

  <b><label>Title</label></b>

  <span>Post title of news story here.</span>

  <input type="text" name="title" size="100" /></p>
  <b>URL</b>

  <span>Post URL of news story here (i.e., <a href="http://www.website.com/storytitle">http://www.website.com/storytitle</a>).</span>

  <input type="text" name="field_id_29" value="" maxlength="200" size="100" /></p>

{if error}
    {error}
{/if}
<b>Tags</b>
<span>We use tags to categorize our content to make it easier to find what you are looking for. Enter as many tags as you feel appropriate. As you begin to enter your tags our system automatically will suggest tags already in our system which matches your entry. We have provided a list of our team-specific tags on the right for your convenience. Some of the more popular tags are displayed underneath the Tag entry box. Only tag an entry as <b>General</b> if no other specific tags apply.</span>

 {field:tag_field}
{if textarea}
  <label><b>Body</b></label>

  <span>b>News Item Lead-In:</b> Only post *NEWS* articles. (News being defined as articles or blog entries from an outside source.) Before hitting the submit button, check to make sure other people didn't just beat you to the punch with an entry on the same subject. Lead-ins which include humor and/or analysis are preferred over the posting of quotes from the linked article. Quotes from linked material should be limited in length as much as
possible. Post enough to get the point across; don't post the entire article.</span>


  <textarea id="field_id_30" name="field_id_30" value="">/textarea>

{/if}
{/custom_fields}

  <label><b>Extended</b></label>

  <span> Use extended field for information you only want to display on the discussion page.</span>

  <textarea id="extended" name="extended" value="">/textarea>

<input type="submit" name="submit" value="Submit" />
{!-- <input type="submit" name="preview" value="Preview Submission" /> --}

</td>
<td> <>

<td valign="top">
<!-- Empty column for now -->
</td>
</tr>
</table>
{/exp:safecracker}

Is there a problem with my template?

I did a little more experimentation. If I use the bug code that Robin suggested, the formatting buttons appear. If I remove jquery using include_jquery=“no” and add my own jquery, they no longer appear. Unfortunately, by removing my own jquery Solspace’s Tag buttons don’t work.

Hi Jim,

Thanks for the extra information!

Are you loading your own jQuery in the <head> of your html? We’ve seen some conflicts resolved by moving the jQuery load to the end of the template, just before the </body> tag.

Try that for me and let me know the result.

One other thing, when you disable your own jQuery, are you seeing the Tag buttons disabled only on the SafeCracker template, or site wide? You can call in the same version of jQuery that SafeCracker uses with the jQuery Module.

Cheers,

I am loading my own Jquery in the head.

[removed][removed]

Are you suggesting the issue may be a jquery version conflict? I’d prefer to not have to make users download a separate copy of jquery than they download when they hit the frontpage, especially for mobile users.

I’ll test using a different version of Jquery to see if that takes care of the issue. Which version does EE use? (I don’t remember seeing this mentioned in the docs, although I may have just overlooked something.)

To answer your question. the Tag button disappear from the Safecracker form.

Hello Jim,

Dan was asking you to move the jQuery load to the end of the template, just before the </body> tag.

Can you try that out and let us know how it goes?

Cheers,