Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: General Setting panel is empty
| Status | Resolved |
| Add-on / Version | Publisher 2.7.3 |
| Severity | |
| EE Version | 3.5.15 |
pixiwooh
Feb 28, 2018
Description:
The General Settings panel is absolutely blank.
I have been asked to disable publisher temporarily to resolve a bug with Forms from DevDemon but I just can’t because of this General Settings issue.
I tried to swith the value to “no” directly in the DB but it causes more trouble…so here I am :D
BoldMinded (Brian)
The general settings page is supposed to look like that. Nothing is wrong. I also removed the temporary disable option bc it was very very difficult to maintain. If you need to debug the forms you’ll need to backup your db and uninstall publisher, then restore the db when you’re done debugging forms.
pixi
Oh 😕
And does the parameter data-publisher-ignored=”yes” is supposed to work with form tags from devdemon’s form? Because I tried to add it but it didn’t change anything and I see that in the source code : data-publisher-updated=”true”. Does the data-publisher-ignored parameter is supposed to turn data-publisher-updated to false? How does that work please?
BoldMinded (Brian)
If you add data-publisher-ignored=”yes” to a form tag, then Publisher will not try to parse it and update any urls that the form tag outputs, thus it won’t translate or add a language prefix to the urls.
pixi
Hi Brian,
to not uninstall everything I installed an older version of publisher (where the switch off was still possible, héhé) and saw that the forms add-on works properly without publisher. So DevDemon team told me to see with you for a workaround. It is something about the URLs but I tried the data-publisher-ignored=”yes” but it doesn’t make any effect.
BoldMinded (Brian)
I’m going to need more information than “its something about the urls” before I can look into this. I’m going to close this ticket so you can make a new one and provide as much detailed information as possible describing the situation, including a link to a demo/dev site where the issue is present, and if possible CP and FTP access. The template that the form is in, don’t put anything else in it, just the bare bones template code to make the issue happen.