Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Option 'name' in CMS_PLACEHOLDER_CONF ignored
See original GitHub issueOption ‘name’ is ignored If template name specified before placeholder name
CMS_PLACEHOLDER_CONF = {
'some_placeholder': {
'plugins': ['TextPlugin'],
'name': 'Some localized name',
},
'some_template.html another_placeholder': {
'plugins': ['TextPlugin'],
'name': 'Another localized name',
},
}
The first work, but the second is not.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Firefox ignores option selected="selected" - Stack Overflow
In firefox, I've notice that the "selected" attribute will not work unless you place the select inside a form, where the form has...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@czpython I’ll take this myself, as I want to check what the new placeholderconf changed in this respect
Confirmed. I’ll send a PR later today