Styling and Linking

Most likely it can be done by using the theme additional CSS function. I am not certain which field you mean.

If you know how to use your browser developer tools you should be able to find the element name to style.

Sorry to not be clear, I meant I need to bold certain words inside the message field, like sub-headers to emphasize sections.

I can’t test this right now, but try putting <strong> before bold text and <\strong> after it. There are some instructions where you enter the petition text from

Let me know how it works.

No, thank you, but I tried that already. I wonder if there’s a way to add a custom field with tinymce. ??

OK, I can see that the customisation I was thinking of was actually for adding name field etc. I will look at some sort of styling options.

I do need to be careful to ensure no malicious code could be included in emails that might be sent to the mayor etc. So this might be limited to bold and italics.

That would be great! Thank you for considering this!

I have released version 2.5.0 which supports markdown in the message to the target.

https://speakout.123host.net.au/markdown

Thank you for doing this. Is is tied to the default style? I’m using the basic style and just gave it a try and the markup displays.

Edit: I switched to the default and have the same result. Would love to get this working if possible.

• This reply was modified 4 years, 5 months ago by jrotem.

The markdown code will display in the message e.g. _italic_ but when the email is sent it should be change to italic

Have you tried that?

I see. We would need to have it display properly on the public website. In fact, my client would prefer not having it than to have it display on the front end, sorry!

We also need to remove the note about styling and markup that shows on the front end, please.

Really appreciate your efforts, though.

• This reply was modified 4 years, 5 months ago by jrotem.

If you don’t want to use markdown, just don’t use it.

I wanted to add an editor, but there are all sorts of problems doing that, this was the best I can come up with that won’t take me too much time.

As for the note about styling, that should only be visible if the message is editable by the user. Surely if they can edit, then giving the opportunity to style the message is a good idea.

Hmmm…I just had a thought. If the message isn’t editable by the user, I should be able to have it display with the formatting rendered as it will appear. Would that work for you?

Aha… my misunderstanding was I assumed we’d be styling on the backend, it would display on the front end, like styling a blog post. But yes, you are correct, we are allowing people to edit when they sign, so now it does make sense that that notification would show. I guess we can’t have both!

I understand about the issues with adding an editor. I’m pretty sure this particular client would rather forgo the styling and leave the ability for signers to edit the text, but without the ability to edit style on the front end and without the extra notification showing publicly. Markup is just not for this particular crowd, I’m afraid. (I was even concerned that the client might find it a learning curve!) I’m sorry for the confusion!

OK. I will release a version where markdown can be disabled. Won’t be today though ;o)

Thanks for all this!

PS I removed the front-end notification via display none. ??

• This reply was modified 4 years, 5 months ago by jrotem.