The project page should mention that you have to disable, then enable, your theme in order to get breakpoints read in from the .info file.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | breakpoints-documentation-clarification-2075595-8.patch | 4.63 KB | jwaxo |
Issue fork breakpoints-2075595
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #1
WarrenK commentedDocumentation should also reference https://drupal.org/node/1869968 where attiks wrote, "At the bottom of the theme settings page you should see a new button to reload the theme info, do you see it?"
Comment #2
attiks commentedComment #3
attiks commentedFrom[#1869968]
A mention of where to find this button in the help text on admin/config/media/breakpoints would suffice to fix this UX bug.
Comment #4
hass commentedI think we do not need to document broken logic #1869968: Can't add/delete theme breakpoints that need to be fixed. That is not worth a doc.
Comment #5
attiks commentedThe documentation is adding a sentence like 'at the bottom of the theme settings page you can find a button to reload the breakpoints of yout theme ...."
Comment #6
jelle_sFixed in latest dev version.
Comment #8
jwaxo commentedHello,
As I wasn't able to find this information in the included documentation with the latest dev version, I completely revamped the very minimal README.txt with a newer one, which also includes this information about reloading the theme when updating breakpoints via the .info file.
Attached is a patch to update README.
I tried to cover a lot of other information that doesn't appear to be laid out anywhere. I'm also trying to update a lot of popular contrib modules as a whole, so if you have any commentary on the documentation style I have laid out here, let me know.
Comment #9
jelle_sComment #10
jelle_sFixed in latest dev version. Thanks for the patch!