The css id generated for the microcontent blocks are of the form "block-microcontent-93" (where 93 is the node id)

For "predefined" microcontents (mission, footer, etc...), having ids of the form "block-microcontent-mission" would provide a more robust way to theme them.

CommentFileSizeAuthor
#3 microcontent.module.patch1.85 KByched

Comments

yched’s picture

edit : more precisely, since the block css id is generated by the theme layer form the block delta,
this would mean having an alphanumeric delta for these blocks.

Bèr Kessels’s picture

Version: 4.7.x-1.x-dev » master

Good idea. All it needs is a patch..... :)

Marked it for CVS, since I dont add features to a stable version (note that HEAD microcontent == 4.7 compatible)

yched’s picture

Status: Active » Needs review
StatusFileSize
new1.85 KB

Allright, here is the patch :-)

note that it will probably ruin the block settings the user had previously set...

Side note : Why do you use 'details' instead of 'footer' for the footer microcontent ?
I kept my patch coherent with that, but I found it strange...

Bèr Kessels’s picture

Status: Needs review » Needs work

1. You are right about the previous settings. I fear we need to ship a .install containing a hook_update :(. setting to "needs work" because IMO it is critical not to break peoples code.

2. Footer indicates a placement, the bottom of the page. However, microcontent allows you to place your details anywere on the site. I chose the name after a naming convention from the world of CSS: http://www.stuffandnonsense.co.uk/archives/whats_in_a_name_pt2.html

yched’s picture

1. install / hook_update : I'm afraid I won't know how to do that :-(

2. 'footer' / 'details' : Right. Thanks.

larowlan’s picture

Issue summary: View changes
Status: Needs work » Closed (outdated)