change form title

[webzunft]

there is no filter for the form title, but one might use the gettext filter to change it
I wouldn’t recommend it though and use .po translation files
but for less tech-savvy users this might be a solution to do

maybe I can suggest a filter on wp org for this, because there is some logic that might be interesting

[havn]

warning, wall of text incoming

Hi Webzunft. I'm a git-hub noob, so I don't know if this is the right place to say something, and I hope I don't violate community guidelines, or offend you in any way..
You can tell me off if needed.

But I noticed your form-title comment and, well, I'm actually working on that at the moment, and i could use some advice. I am in the process of expanding this plugin (by Thomas Maier -> is that you?) because I need extra options and, never having made a WP plugin ever, expanding this one seemed like a good starting point. I am learning as fast as I can from Thomas'original code, and am pretty far with regard to the settings pages (what I have, works, but it doesn't look pretty on the inside yet), but I lack knowledge in how to properly program it, and how to connect it all to the rest. Meaning how to connect the new options to Thomas' plugin core. Simple stuff already works: I can set & save the new options on both pages (and saving page 2 works without erasing the settings of page 1 and vice versa, yey) and doing it all in the same way as the original plugin does it.
What I am making:

General settings (page 1):

• Form title / reply button title (text-input)
• Submit button text (text-input)
• Required fields: name, email, website, message (4 checkboxes)
• Remove website field (original plugin option)
• Remove email field (original plugin option)
• Remove default texts (original plugin options)
• Text-before / text-after (original plugin options)
• Hidden fields with all options of page 2 (many hidden fields)

CSS/Layout settings (page 2):

• Layout option 2 columns (original plugin option)
• CSS options:
  • Use custom css stylesheet option (checkbox)
  • Custom stylesheet location (local/theme css folder or external url) (text-input)
  • Custom primary color (text-input)
  • Custom secondary color (text-input)
  • Option to use these colors on frontend/backend or both 2 radio buttons)
    (no idea why I made that, it's just a study project)
• Hidden fields with all options of page 1 (many hidden fields)

Ideas for more styling options:

• form background-color
• form border
• form border-radius
• form box-shadow
• maybe form background-image (actual image or linear gradient)
• thinking about a modal version (pop-up-comment-form)...
• not saving the user IP{ (that's a good idea, thanks!)

And my other farfetched plan is to add field-sizes (width, height) with a html5 range-sliders - and have a preview version of the comment form below the css options so one can actually see right away whats happening. That should make styling very comfortable: no setting a value/saving/going to the frontend to see the result/rinse and repeat.

Unfortunately the shortcode provided only works in the frontend and I haven't yet figured out how to use a 'new main class' object to make the shortcode available on a settings page. So Ill work with a dummy form coming week. Actually, I have never written a php class or made a wp plugin, and studying by example works, but it takes more time than I'd like. So iIf you have any pointers or advice that would be really great. I added 2 screenshots of what I'm looking at right now. It works locally and it looks pretty, as long as you don't peek under the hood haha. Anyway...

Have a great day, and a splendid 2023 :-D

Hans

[webzunft]

Hey @havn. Thanks for reaching out. I learned a lot from others, too. However, there are better ways to ask for help than commenting on a somewhat unrelated issue in GitHub. You can fork my Comment Form plugin on GitHub and add your own code. You could start pull requests if you think some of your features are useful to users and you want them added to my plugin and reviewed as well. I cannot promise a quick reply, though, since I might have other priorities.
I am not seeing a specific question from you. Just reviewing is hard without knowing more or seeing the code. I don’t think shortcodes are supposed to work in the backend, and I have not looked into workarounds for that. I am sure you will find something when googling.