Difference between revisions of "Talk:Drupal"

From Organic Design wiki
(→‎Security: access control mechanism must refer to Organic Group Module)
m
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
== Security ==
+
From practice, the following notes:
−
''However, sites that are using the Organic Groups module discussed above '''has''' its own access control mechanism based on the group structure which is more appropriate for sites already using that module.''
 
  
−
; no main verb
+
Skinning procedures are generic HTML/PHP/CSS/JavaScript and no big deal. JQuery is now default.
 +
*You need to add page.tpl.php from the starterkit and edit that along with the chosen layout css if you want to make changes outside the block administration.
 +
*For a different front page skin, create and edit page-front.tpl.php and create and link to a front-page css loaded after the other scripts.
 +
*If you want to make any sort of new region on a page, the code in the Zen-based skin has to be refactored into tables, as IE7 loses the plot with the negative margins in the div-only version.
 +
*The best way to patch modules is with Linux, then transfer them to Windows machines if required. For example:
 +
**OG Forums for security
 +
**Webform Reports for added functionality
  
−
*There is no verb forming a grammatical sentence. To try to understand the intended statement, it is first necessary to resolve the dependent clauses:
+
--[[User:Jack|Jack]] 16:17, 16 June 2011 (PDT)
−
 
 
−
; ambiguity
 
−
 
 
−
*There is an unresolvable ambiguity here for the non-expert reader (myself included).
 
−
 
 
−
:It is unclear to me what the intended referent of '''has''' is in the paragraph
 
−
 
 
−
:There are 2 possible ways to parse this:
 
−
 
 
−
*parallel subordinate clauses
 
−
 
 
−
The first subordinate clause is ''restrictive'', but contains an ''expansive'' subordinate sub-subclause
 
−
 
 
−
:Since the subject, ''sites'', is plural, it appears that ''access control mechanism'' refers to ''organic groups module'' ; if so, a subordinating conjunction is needed:
 
−
 
 
−
*... sites
 
−
**that are using the Organic Groups module discussed above (restrictive) - select subset of all sites
 
−
***, '''which''' has its own access control mechanism based on the group structure... [expansive] - provide further detail about ''module''
 
−
 
 
−
> sites (using module [module has mechanism] )
 
−
 
 
−
:This subordinate clause is followed by another subordinate clause about something ''appropriate'', the antecedent of which is unclear:
 
−
 
 
−
* ... structure is appropriate
 
−
 
 
−
> sites (using module [module has mechanism [mechanism is based on structure [structure is appropriate] ] ] )
 
−
 
 
−
:sites that use module, which has mechanism, which is based on structure, which is appropriate
 
−
 
 
−
:''a'' that ''b'', which ''c'', which ''d''
 
−
 
 
−
* an unwieldy and unlikely chain of dependent clauses.
 
−
 
 
−
* mechanism is appropriate {for sites}
 
−
 
 
−
> sites (using module [module has mechanism [mechanism is based on structure] + [mechanism is appropriate] ] )
 
−
 
 
−
:''a'' that ''b'', which ''c'' + ''b'', which ''d''
 
−
 
 
−
; if ''c'' and ''d''  are parallel, both referring to ''module'',  a conjunction is required:
 
−
 
 
−
: sites that use module, which has mechanism, which is based on structure and which is appropriate
 
−
 
 
−
> sites (using module [module has mechanism [mechanism is based on structure] and [structure is appropriate] ] )
 
−
 
 
−
:This produces awkward nested dependent clauses, [b, which c, which d] - grammatically forbidden in English.
 
−
 
 
−
:The solution is to refactor by promoting the second [expansive] dependant clause to an adverbial of  the main clause, and which refers to the first a (restrictive)  subordinate:
 
−
 
 
−
> sites (using module [module has mechanism [mechanism is based on structure]  : {structure is appropriate} ] )
 
−
 
 
−
> sites (using module [module has mechanism [mechanism is based on structure] ] : {mechanism is appropriate} )
 
−
 
 
−
> sites (using module [module has mechanism [mechanism is based on structure] ] ) : {module is appropriate}
 
−
 
 
−
> {module is appropriate} for sites (that use module  [since module has mechanism [based on structure] ] )
 
−
 
 
−
However, it is more appropriate for sites that are already using the Organic Groups module discussed above, since it has its own access control mechanism based on the group structure.
 
−
 
 
−
 
 
−
--[[User:Infomaniac|Infomaniac]] 18:24, 19 January 2011 (PST)
 

Latest revision as of 23:17, 16 June 2011

From practice, the following notes:

Skinning procedures are generic HTML/PHP/CSS/JavaScript and no big deal. JQuery is now default.

  • You need to add page.tpl.php from the starterkit and edit that along with the chosen layout css if you want to make changes outside the block administration.
  • For a different front page skin, create and edit page-front.tpl.php and create and link to a front-page css loaded after the other scripts.
  • If you want to make any sort of new region on a page, the code in the Zen-based skin has to be refactored into tables, as IE7 loses the plot with the negative margins in the div-only version.
  • The best way to patch modules is with Linux, then transfer them to Windows machines if required. For example:
    • OG Forums for security
    • Webform Reports for added functionality

--Jack 16:17, 16 June 2011 (PDT)

Retrieved from "https://organicdesign.nz/wiki/index.php?title=Talk:Drupal&oldid=102333"