Conditional comments in templates

Similar Questions

• Conditional comments in DW templates

  I started to use the conditional comments these days to help target CSS to IE6 and IE7, however Dreamweaver does not appear to understand the links related to the conditional comments and so don't update when used in a template on a site.
  
  For example, if I have:
  
  <!-[if lte IE 6] >
  "" < link href = "... / assets/css/screen-ie6.css" rel = "stylesheet" type = "text/css" media = "screen" / >
  <! [endif]-->
  
  In a model, usually in the code HTML the relative to the CSS path will update on several pages of the site. But none so if it is in a conditional comment. Instead, I have to use the absolute path ' / assets/css/screen-ie6.css ' which has then stops fully test me the local site on my PC.
  
  Anyone know of a way around this? Or is it to Adobe to make an update for DW for relative pathnames can be re-writings in the DW templates (which would be fine)...
  
  Best wishes
  Simon

  Of course I do!

  http://www.Adobe.com/cfusion/mmForm/index.cfm?name=wishform

  --
  Murray - ICQ 71997575
  Adobe Community Expert
  (If you * MUST * write me, don't don't LAUGH when you do!)
  ==================
  http://www.dreamweavermx-templates.com - template Triage!
  http://www.projectseven.com/go - DW FAQs, tutorials & resources
  http://www.dwfaq.com - DW FAQs, tutorials & resources
  http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
  ==================

  "Studio 24" wrote in message
  News:elu5b7$372$1@forums. Macromedia.com...
  > just enough - do you know if there is anywhere I can ask Adobe for this
  > feature to be added to a future version of DW?

• Conditional comments

  I have a few questions about conditional comments. First of all, they work only for Internet Explorer, right? So, if I have something like:

  <!-[if lt IE 9] >

  < p > Hi there! < /p >

  <! [endif]-->

  All modern browsers will see as a comment and move on, right?  Older versions of Explorer don't recognize (a) the comment syntax and see the greeting, or (b) just look like a conditional comment that they are supposed to run if they are IE8 or more?

  What happens if the old versions of Firefox running through it, or an old version of a non - IE browser...  Are they see it as a comment, or what will happen? Something bad?

  Thank you!

  Standard as HTML comments have always existed and were always ignored by browsers.

  The conditional as comments is ignored as a standard comment.

  Make sure you just never use you two - at the beginning and at the end of your comments, things like can cause validation problems.

• Using conditional comments for IE7

  I'm working on my first attempt to apply a conditional comment. My page seems correct in the lab browser for all browsers except IE7, who needs a change of left padding on a particular div. My main css for this div looks like this:

  #div {}

  padding-top: 192px;

  padding-left: 138px;

  height: 38px;

  Width: 120px;

  position: relative;

  }

  I have the addition, after the beginning of the div tag in the HTML code:

  <!-[if IE 7] >

  < style type = text.css >

  #div {padding-left: 100px ;}}

  < / style >

  <! [endif]-->

  As I understand it, the main css instructions is still in effect, that only the left padding will change. But when I view the page in the lab browser, the comment by the State has no effect. What Miss me?

  Hello

  The style of text scrolling is done via the "text_scroll.js" JavaScript file and that's why you can not style using css, the script file has also said that it should not be used as an external file (should be on the page, not a link).

  I also noticed that the JavaScript is on the web site of dynamic disk and this site is known for providing the code that only works in specific browsers, it's just one of the reasons why I would suggest looking for other JavaScript code.

  PZ

• Conditional comment CSS Hack for IE6

  Hi, I'm trying to circumvent an IE6 display problem and I tried to use a conditional comment in the head tag to load a specific stylesheet for IE6. Here is my code:
  
  < link href = "css/normal.css" rel = "stylesheet" type = "text/css" / > "
  <!-[if IE 6] >
  "< link href="css/ie-6.0.css "rel ="stylesheet"type =" text/css"/ >
  <! [endif]-->
  
  For some reason any IE6 ignores this.
  
  If I remove the '6' instruction conditional IE6 is applied to the style sheet, but does any other version of IE browsers that isn't what I want.
  
  After searching on the net, put IE 6 should work, but for some reason, this isn't for me.
  
  Any help would be appreciated.
  
  LAGooner

  Huh. I guess it must be the IE6 version I use. I downloaded IE Tester http://www.my-debugbar.com/wiki/IETester/HomePage (worth download incidentally) and the hack works great.

  Thank you for taking the time to look at it for me.

  LAGooner

• Cannot use the Upce with Centos64 comments or template customization

  Hello

  I'm trying to deploy a new Centos 6.X 64 comments using a technique of customization. I built the reference VM with a single ext3 partition and the swap partition. I installed the version of VM Tools that is listed as current. When I try to use the specification of customization, I prepared the selection is grayed out with the message:

  "The personalization of the guest operating system"centos64guest"is not supported in this configuration. Customers Microsoft Vista and Linux with a logical volume Manager are only for the recent host ESX and VMware Tools versions support"

  I am running:

  vCenter 5.0 build 913577

  ESXi 5.0 build 914586

  The customer does not use an LVM. Here is the output of "-l parted."

  Model: Virtual disk in VMware (scsi)
  Disk/dev/sda: 107 GB
  (Logical or physical) sector size: 512 512 b/b
  Partition table: msdos

  Number start end size Type file system flags
  1049kB 1 GB 101 101 GB ext3 primary bunch
  2 GB 101 107 GB 6443 MB linux-swap (v1) primary

  I review the comments of Linux requirements and have not been able to find out what I'm doing wrong here. Can someone tell me please in the right direction?

  Only the operating systems listed in this guide are officially supported for customizing the vCenter guest operating system:

  http://PartnerWeb.VMware.com/programs/guestOS/guest-OS-customization-matrix.PDF

  Unfortunately, CentOS is not among them and vCenter will refuse to apply the customization of virtual machines that are configured for CentOS. However, you can easily get around this by setting the configuration option of the machine virtual guest to the corresponding version of RHEL operating system. This should cause problems for normal operations of VM, but you can replace it on CentOS after customization if you want to be sure.

  LVM or normal partition scheme should without importance for the success of the customization process itself.

• Manipulate the values of the variables to trigger conditional comments

  7.01.237 on Win 7 Pro PC work.

  Try to implement the following:

  3 responses to survey on a single slide type (think likert with a scale of 1 to 10)

  At the end of each of the three questions, select a "submit" button, and give your comments, based on a predetermined for possible values range (between 3 and 30)

  Tried setting up of three variables (Q1, Q2, and Q3) and seen the answer buttons to assign a value of 1 to 10 for each variable, then have the total submission button of the Q1, Q2 and Q3 values:

  

  and then display the appropriate text based on the number:

  

  no luck. Tried using the action of the increment to add to the overall value of Total_Q, then perform the masking based on the new value, not going either.

  Cannot use "a part of the quiz" because it may in fact be a quiz marked.

  Any ideas? I think that I'm not seeing the forest for the trees at this stage.

  Justenuf

  Try to follow the variables in a text container, do not know how you fill at all. Likert questions does not normally give rise to a score. Once, I wrote a blog about the use of multiple CHOICE for obtaining scores for a type of Likert question:

  http://blog.lilybiri.com/graded-survey

• Syntax HTML 5 comment

  I'm looking for a way to add comments to HTML 5, text of meaning is not running, but is there to help understand the programming. I see not in CSS / * comment * / used for this purpose. In HTML, I see the comments, but it is unclear how they are reported comments.

  For example, I saw <! - comment - >, but this syntax also seems to be used for conditional instructions which are executed, as in <!-[if gt IE 8] > <!-->. That looks like it is written in a comment, but obviously, it's supposed to be run. I think so. I just want to be able to quietly add comments in the HTML code, but I need help with the syntax. Thank you!

  So far, you've got everything right.

  / * This is a CSS comment * /.

  It is a single line comment in JavaScript or PHP code

  The conditional comments for IE are ignored by all browsers except IE9, 8, 7, 6.

  IE10 pays more attention to the conditional comments.

  Nancy O.

• Hide a div on condition

  I have an annoying < div > that appears on Internet Exploder. For the reasons covered elsewhere, I want hidden.

  A < div > hides well. The other is stubbornly visible in IE and I don't want that, except in the context of IE9.

  Here is the page:

  http://www.hollisinternetmarketing.NET/Patty/patty1.html

  And here's what I've done in CSS:

  < style media = "all" >

  <!-[if lte IE 8] >

  {#centertab}

  visibility: hidden;

  display: none;

  }

  {#amazon_scroller}

  visibility: hidden;

  }

  <! [endif]-->

  < / style >

  Obviously, I'm trying to hide the ID #centertab of everything Microsoft did before Internet Exploder 9. Just visibility: hidden; works great for the div #amazon_scroller. It does not work for #centertab.

  Why? How can I hide this puppy?

  That should be enough for the two-

  Note that the conditional comment should be on the OUTSIDE of the

• Coding of your Web site is Compatible with IE by using a conditional statement?

  Hi all

  I'm really bad make my site compatible with Internet Explorer. I know, it does not support the element ' position: fixed ' (which I used), but I heard there was a way around this by inserting a "conditional statement". But I'm really, really difficult to code correctly. Where exactly in the HTML code I place it, and how does the browser know what layer/div, it is assigned to?

  Here is the code that defines the changes in IE. As it is, it actually doesn't work properly... it just removes all items on the page... so I know that I made a mistake somewhere.

  <!-[if IE 6] >

  position: absolute;

  top: 20px;

  left: 20px;

  <! [endif]-->

  I don't always know where place them, and how to ensure IE knows what is the code. Can someone help a newbie? I'm way too deep! Www.ameliaharris.110mb.com/ of the Web site if it is of no use.

  Thanks in advance.

  I had a peek at the CSS on your site, and it uses some of the strangest buildings I've ever seen. For example:

  unicode-bidi:bidi-override; direction:rtl;
  

  What on earth that is all about?

  Again, to answer your question, what you are doing wrong with the IE conditional comment, is that it is incomplete. The conditional comment must contain a block of complete style with the regular style rules:

  Because you want to override what is in your style sheet, it should come theof the embedded document after links to CSS and external style sheets.

• Conditional models PLSQL

  are there references on how to write conditional statements in templates?

  Hello

  This help you?

  http://www.Oracle.com/technology/pub/notes/technote_htmldb_format.html

  Note: He is old, but gives an idea ;-)

  Kind regards
  Iloon

• Model column name - report Conditions of region

  All,
  
  Is it possible to PL/SQL conditions associated with regions that use the COLUMN NAMED models. I already have some conditions in my template, but I wanted the flexibillity to hide and show columns based on other criteria in the report area. I have enough conditions to implement the conditions in the definition of the model. When I put a condition in the report he ignores it. I even tried to never put on the condition and he always showed the column.
  
  Thank you
  
  Tom

  Hello

  The release of the report model named column is based directly on data SQL itself, so such a condition would not make much difference.

  What you could do is assign a class to each TH and TD tag within the model and then conditionally display or hide the column by updating the style of class (use the display: None style to hide the column). I did it here: [http://apex.oracle.com/pls/otn/f?p=267:118]

  Andy

• Then apply a pattern updated the content overlaps the previous contents

  Hello

  Massive headacke side... I really need to solve this problem – work on the line.

  I'm trying to update a site created by my predecessor offline. I've updated the model used, which created an insane amount of problems, more including fixed like today. When you try to update a single page using the template, the content of overlap. I find myself with 2 headers, footers 2 etc...  I thought it was because all the documents on the site (total 53, not too big) are detached from all models and the name of the editable regions on the documents do not exist, but even trying to match the areas to move the contents to the new regions just made a mess of things. My goal (I hope) is too simply update the site without going through all those contents that overlap. Please help, everybody.

  Here is my template code:

  <! DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional / / IN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" > ""
  "< html xmlns ="http://www.w3.org/1999/xhtml">".
  < head >
  < meta http-equiv = "Content-Type" content = text/html"; charset = utf-8 "/ >"
  < title > QMS: AFM < /title >
  < style type = "text/css" >
  <!--
  {body
  Police: 100% Verdana, Arial, Helvetica, without serif.
  Background: #666666;
  margin: 0; / * It is advisable to zero, the margin and the filling of the body to hold element has a different default browser * /.
  padding: 0;
  text-align: center; / * This centers the container in IE 5 * browsers. The text is then set left aligned by default in the #container selector * /.
  Color: #000000;
  background-color: #D7D7D7;
  background-repeat: repeat-x;
  border-bottom-color: #066;
  border-right-color: #066;
  border-bottom-color: #066;
  border-left-color: #066;
  }

  / * Tips for Elastic layouts
  1. Since the elastic layouts overall size is based on the user's default font size, they are more unpredictable. Used correctly, they are also more accessible for those who need larger fonts given the length of the line remains proportionate.
  2. sizing of the divs in this provision are based on 100% font size in the body element. If you decrease the overall size of the text by using a font size: 80% on the body element or the #container, remember that the complete provision will reduce proportionally. You can increase the widths of the divs to compensate for this.
  3. If the sizing of fonts is changed in different quantities on each div instead of on the overall design (ie: #sidebar1 is a font size of 70% and #mainContent has a font size of 85%), this will change proportionally each of the overall size of divs. You can adjust the base on your final sizing of fonts.
  */
  .twoColElsLtHdr #container {}
  Width: 46em;  / * This width will create a container that can fit in a 800px browser window if text is left to default browser font sizes * /.
  background: #FFFFFF;
  margin: 0 auto; / * margins (in conjunction with a width) auto Center the page * /.
  border: 30px no #C4C4C4;
  text-align: left; / * This setting overrides the text-align: center on the body element. */
  padding-left: 10px;
  background-color: #FFF;
  border-bottom-color: #C4C4C4;
  border-right-color: #C4C4C4;
  border-bottom-color: #C4C4C4;
  border-bottom-style: outset;
  border-left-style: outset;
  border-top-width: thick;
  border-right-style: outset;
  border-top-style: outset;
  border-left-color: #C4C4C4;
  border-right-width: thick;
  border-bottom-width: thick;
  border-left-width: thick;
  }
  .twoColElsLtHdr #header {}
  padding: 0 10px;  / * This filling is the alignment to the left of the items in the div that appear below. If an image is used in the #header instead of text, you can remove the padding. */
  background-color: #FFF;
  }
  .twoColElsLtHdr #header h1 {}
  margin: 0; / * zero setting of the margin of the last element in the #header div tag will prevent the collapse of margin - inexplicable space between divs. If the div has a border around it, this isn't necessary, which also allows to avoid the collapse of margin * /.
  padding: 10px 0; / * padding instead of margin will allow you to keep the edges of the div element * /.
  }

  / * Sidebar1″ tips:
  1 be aware that if you set a value for the font size on this div, the width of the div will be adjusted accordingly.
  2. as we work in ems, it is preferable not to use the filling in the sidebar itself. It will be added to the width for browsers compatible standards creating a real unknown width.
  3. the space between the wall of the div and the items it contains can be created by placing a margin left and right on these items as seen in the rule ".twoColElsLtHdr #sidebar1 p.
  */
  {.twoColElsLtHdr #sidebar1}
  float: left;
  Width: 12em; / * the background color will be displayed for the length of the content of the column, but no further * /.
  Padding: 15px 0; / * upper and lower padding create a Visual space within this div * /.
  background-color: #066;
  background-repeat: repeat-x;
  border-top-width: thin;
  border-top-style: none;
  border-right-style: none;
  border-bottom-style: none;
  border-left-style: none;
  border-right-width: thin;
  border-bottom-width: thin;
  border-left-width: thin;
  color: #FFF;
  padding-left: 0px;
  Clear: left;
  }
  H3 .twoColElsLtHdr # sidebar1″, .twoColElsLtHdr #sidebar1 p {}
  margin-left: 10px; / * the left and right margins should be to all of the items that will be placed in the side columns * /.
  margin-right: 10px;
  background-color: #066;
  text-decoration: inherit;
  }

  / * MainContent tips:
  1. If you give this div #mainContent a value of different size of the div # sidebar1″, the margins of the #mainContent div will be based on the font size and the width of the div #sidebar1 depend on the size of the font. You can adjust the values of these divs.
  2. the space between the mainContent and sidebar1″ is created with the left on the mainContent div margin regardless of how content div the sidebar1″ contains, the space of the columns will remain. You can remove the left margin if you want the #mainContent div text to fill the space of #sidebar1 when the content of #sidebar1 is complete.
  3. to avoid falling of float, you may have to test to determine the size of the image/approximate maximum element because this provision is based on the calibration of fonts the user combined with the values that you set. However, if the user has their browser game lower than normal font size, less space will be available in the #mainContent div that you see on the test.
  4. in the Internet Explorer conditional comment below, the zoom property is used to give the mainContent "hasLayout". This avoids several specific IE bugs that may occur.
  */
  {.twoColElsLtHdr #mainContent
  margin: 1.5em 0 0 13em; / right margin can be given in pixels or ems. He created space on the right side of the page. */
  color: #069;
  background-color: #FFF;
  border-top-style: none;
  border-right-style: none;
  border-bottom-style: none;
  border-left-style: none;
  }
  .twoColElsLtHdr #mainContent a: link {}
  text-decoration: none;
  color: #069;
  }
  .twoColElsLtHdr #mainContent a: visited {}
  text-decoration: none;
  color: #069;
  }
  .twoColElsLtHdr #mainContent a: hover {}
  text-decoration: underline;
  color: #069;
  background-color: #FFF
  }
  .twoColElsLtHdr #mainContent a: active {}
  text-decoration: none;
  color: #069;
  }
  .twoColElsLtHdr #footer {}
  padding: 0 10px;
  line-height: 0pt;
  color: #069;
  background-color: #FFF;
  do-size: 10px;
  }
  .twoColElsLtHdr #footer p {}
  margin: 0; / * zero setting the margins of the first element in the footer will avoid the possibility of the collapse of the margin - a space between the div tags * /.
  padding: 10px 0; / * padding on that element will create space, just as it would the margin, free margin collapse question * /.
  background-color: #FFF;
  }

  / * Various classes for reuse * /.
  .fltrt {/ * this class can be used to float right to the item in your page.} The floating element must precede the element it should be next to the page. */
  float: right;
  left margin: 8px;
  }
  .fltlft {/ * this class can be used to float an element on your page to the left * /}
  float: left;
  right margin: 8px;
  }
  .clearfloat {/ * this class must be placed on an element div or break and should be the last item before closing a container should completely contain a float * /}
  Clear: both;
  height: 0;
  font size: 1px;
  line-height: 0px;
  }
  H1 {}
  color: #069;
  do-size: 16px;
  border-bottom-color: #069;
  border-top-width: thin;
  border-right-width: thin;
  padding-right: 0px;
  padding-left: 0px;
  }
  body, td, th {}
  do-family: verdana;
  text-decoration: none;
  color: #069;
  border-bottom-color: #069;
  border-right-color: #069;
  border-bottom-color: #069;
  border-left-color: #069;
  border-top-style: solid;
  border-right-style: solid;
  border-bottom-style: solid;
  border-left-style: solid;
  border-top-width: thin;
  border-right-width: thin;
  border-bottom-width: thin;
  border-left-width: thin;
  }
  a: link {}
  text-decoration: none;
  color: #FFF;
  }
  a: visited {}
  text-decoration: none;
  color: #FFF;
  }
  a: hover {}
  text-decoration: underline;
  color: #FFF;
  background-color: #;
  background-repeat: repeat-x;
  background-position: center;
  border-bottom-color: #069;
  border-right-color: #069;
  border-bottom-color: #069;
  border-left-color: #069;
  }
  a: active {}
  text-decoration: none;
  color: #FFF;
  border color: #FFF;
  padding-left: 20px;
  }
  ->
  < / style > <!-[if IE] >
  < style type = "text/css" >
  / * place patches css for all versions of Internet Explorer in this conditional comment * /.
  .twoColElsLtHdr #sidebar1 {padding-top: 30px ;}}
  .twoColElsLtHdr #mainContent {zoom: 1; padding-top: 15px ;}}
  / * the owner above zoom gives IE the hasLayout property, avoid several bugs * /.
  < / style >
  <! [endif]-->

  "" < link href = "file:///U|/AFM/Dreamweaver/Left sidebar.css" rel = "stylesheet" type = "text/css" / >
  < / head >

  < body link = "#006699" class = "twoColElsLtHdr" >
  < div id = "container" > <!-TemplateBeginEditable name = "Header"->
  < div id = "header" >
  "" "" < h1 > < img src = "file:///P|/RPS/AFMS/Quality Management System/QMS website/ENGLISH SITE/Assets/pwgsc-e.gif" width = "364" height = "33" align = "left" alt = "wordmark" / > < img src = "file:///P|/RPS/AFMS/Quality Management System/QMS website/ENGLISH SITE/Assets/wordmark_canada.gif" width = height "83" = "21" align = "right" alt = "wordmark2" / > < / h1 >
  < p > < / p >
  "" "< p > < img src ="file:///P|/RPS/AFMS/Quality Management System/QMS website/ENGLISH SITE/assets/AFM QMS features "width ="709"height ="80"alt ="banner"border ="0"/ > < a href ="mailto:[email protected] "" > < img src = "file:///P|/RPS/AFMS/Quality Management System/QMS website/ENGLISH SITE/Assets/Contactus-e.JPG" width = "110" height = "21" alt = 'contactus-e' border = '0' "/ > < /a > < img src ="file:///P|/RPS/AFMS/Quality Management System/QMS website/ENGLISH/elements of " "" SITE / French - e.JPG "width ="115"height ="21"alt = 'french-e' border = '0' / > < a href ="file:///P|/RPS/AFMS/Quality Management System/QMS website/ENGLISH SITE/ContinualImprovement - e.html "" > < img src = "file:///P|/RPS/AFMS/Quality Management System/QMS website/ENGLISH SITE/Assets/Help-e.JPG" width = "115" height = alt '21' = 'help-e' border = '0' "/ > < img src ="file:///P|/RPS/AFMS/Quality Management System/QMS website/ENGLISH SITE/Assets/Search-e.JPG "width ="115"height ="21"alt = 'search-e' border = '0' / > < /a >" "< a href ="http://source.tpsgc-pwgsc.gc.ca "" > < img src = 'file:///P|/RPS/AFMS/Quality Management System/QMS website/ENGLISH SITE/Assets/thesource.jpg "width ="120"height ="21"alt ="TheSource"border = '0'" / > < img src = "file:///P|/RPS/AFMS/Quality Management System/QMS website/ENGLISH SITE/Assets/Home-e.jpg" width = "104" height = "21" alt = 'Host-e' border = '0' / > < /a > < /p > "
  < p > < / p >
  < / div >
  <! - TemplateEndEditable - >
  < div class = "twoColElsLtHdr" id = "sidebar1″" >
  "" < p > < a href = "... / HOME QMS/QMSHome - e.html" > < strong > home QMS < facilities > < /a > < /p >
  < hr / >
  "" < p > < a href = "... /ABOUTAFM/AboutAFM-e.html" > < strong > on AFM < facilities > < /a > < /p >
  < hr / >
  "" < p > < a href = "... /AdminProcedures/AdminProcedure-e.html" > < of strong administrative procedures > < / strong > < /a > < /p >
  < hr / >
  "" < p > < a href = "... /BusinessUnits/BusinessUnits-e.html" > < strong > < /a > < /p > < facilities > business units
  < hr / >
  "" < p > < a href = "... /POINTSOFINTEREST/pointsofinterest-e.html" > < strong > < facilities > < /a > < /p > Points of interest
  < hr / >
  "" < p > < a href = "... /Achievements/Achievements-e.html" > < strong achievements > < / strong > < /a > < /p >
  < hr / >
  "" < p > < strong > < a href = "... /MeasuringPerformance/measuringperformance-e.html" > measuring Performance < /a > < / strong > < / p >
  < hr / >
  "" < p > < a href = "... /References/References-e.html" > < strong references > < / strong > < /a > < /p >
  < hr / >
  "< p > < a href ="file:///P|/RPS/AFMS/Quality Management System/QMS website/ENGLISH SITE/ContinualImprovement - e.html "> < continuous improvement strong > < / strong > < /a > < /p >"
  < hr / >
  Corners of strong regions > < p > < < / strong > < / p >
  < / div >
  <!-TemplateBeginEditable name = 'Body'->
  < div id = "mainContent" >
  Header < h2 > < / h2 >
  Paragraph < p > < /p >
  Sub header < h1 > < / h1 >
  < p > < / p >
  < h1 > < / h1 >
  < h2 > < / h2 >
  < h1 > < / h1 >
  < p > < / p >
  < h2 > < / h2 >
  <!-end #mainContent->
  < / div >
  <! - TemplateEndEditable - > <!-this element of compensation should immediately follow the #mainContent div in order to force the #container div to contain all the child-> fleet
  
  < br class = 'clearfloat' / >
  < /p >
  <!-TemplateBeginEditable name = "Footer"->
  < div id = "footer" >
  < hr width = "100%" size = "8" noshade "noshade" color = "#006666" id = = "color = & quot; 069 & quot; "color ="#069"/ >
  < p > < strong > followed by: ASQM < facilities > < / p >
  < p > < strong > updated: 25-03-2013 < facilities > < / p >
  <!-end #footer->
  < / div >
  <! - TemplateEndEditable - > < script type = "text/javascript" >
  <!--

  ->
  < /script >
  < / h3 >
  <!-end #container->
  < / h3 >
  < / div >
  < script type = "text/javascript" >
  <!--

  ->
  < /script >
  < / body >
  < / html >

  Make sure you have editable regions in the body of your template set properly before you start it. Also, make sure that you have made a backup copy of your current site (copy the ROOT folder and paste it somewhere on your disk).

  OK - Here's what you need to do:

  0 make a backup of your current website (copy the ROOT folder and paste it somewhere on your disk).

  1. create a new page in your current template (file > New > Site templates > (Site) > (model selection) > Create.) Make sure the checkbox "Update Page when the template is changed" is checked.

  2. thanks to this new page open, open page 1 of 51 pages and copy and paste the contents of each editable area of page 1 in the same area can be changed to your new page.

  3. close page 1.

  4. save the new page with the name of the page of 1 so that the old page 1 is replaced by a new one.

  5. Repeat this operation for all 51 pages.

  Sorry, it's so tedious, but in the end, you will once more a fully controlled model site.

  Moreover, before leaving page 1 and the graphs closing this file, please post here any questions you may have.

• Change the background color of a region, I can only change the box with text

  Hello. First of all, sorry for my English.
  
  I created a new model of the region in my application and I want to change the entire background to silver color.
  After reading the forum, I tried this:
  
  body = background-color: Silver;
  
  in "attributes in Table form.
  
  It works, but only the area with text are silver. I want the entire region with a background silver, (like a scratch on the screen, with black labels).
  
  My region are copied from the region of breadcrump and there the next CEB code:
  
  < div class = 'wire of Ariane-region' id = "' #REGION_STATIC_ID # ' #REGION_ATTRIBUTES # > #BODY # < / div >"
  
  I also tried putting < body bgcolor = "gray" > in several places, but never with the same results.
  
  Another question. I created a theme in my themes of the workspace to play with it, but... where are the files of ccs? they are not in "/ i/themes"... .and as part of the apex I don't see a way to change the footer, and an other things I want to do.
  
  Published by: Andres Vilallave on February 15, 2012 16:14

  Andres Vilallave wrote:
  Yes!, it works...
  Well, I think I have more visual changes now... (God thank you...)

  Good.

  But I want to learn more about the themes...
  I would like to change the theme 4, "Topaz".
  As you say, I created a copy of the file ' i/themes/theme_4"as"i/themes/my_theme_4 ".

  I have said "+ are not... create new files there as these can be changed by future updates APEX. Create your own theme folder. + ", i.e. to use a different physical location, which is referenced by another virtual folder (depending on the architecture of the Web server used).

  Then I created a new theme based on theme4 in my workspace as "my"Topaz". "" My Topaz"" theme is now available in the repository of the theme in "custom themes.
  Now I can change the templates, etc., but the css files what, image files, etc., are My_Topaz to help? Are ¿where?.
  Guess as you say I need to link "" My Topaz"" theme in the my_theme_4 folder, by assigning files in the models of the apex, how can I I do this?

  The definition of header for each page template in the theme contains elements of binding that reference the URL of the CSS as style sheets:

  These must be changed to refer to the new URL CSS files:

  Notice that the page templates use conditional comments to provide additional style sheets with CSS hacks and fixes for broken Microsoft browsers.

  Some other models can also reference image etc. of localities in theme files (although this is less common in the APEX 4.0 + themes).

• Problem in responive Photo Gallery

  I inserted the yoxview photo library of this website http://www.yoxigen.com/yoxview/. Here's the code.

  <! doctype html >

  <!-[if lt IE 7] > < class = "oldie ie6" html > <! [endif]-->

  <!-[if IE 7] > < class = "ie7 oldie" html > <! [endif]-->

  <!-[if IE 8] > < class = "ie8 oldie" html > <! [endif]-->

  <!-[if gt IE 8] > <!-->

  "< class html =" "> <!-InstanceBegin template="/Templates/Vestrytemplate.dwt ' codeOutsideHTMLIsLocked = 'false'->

  <!-<! [endif]-->

  < head >

  < meta charset = "utf-8" >

  < meta name = "viewport" content = "width = device-width, original scale = 1" >

  <!-InstanceBeginEditable name = "doctitle"-->

  < title > < /title > photo library

  < script type = "text/javascript" src = "yoxview/yoxview - init.js" >

  < /script >

  < script type = "text/javascript" src = "yoxview/yoxview - nojquery.js" > < / script >

  < script type = "text/javascript" >

  $(document) .ready (function () {}

  $("#thumbnails").yoxview ({}

  backgroundColor: 'Blue ',.

  playDelay: 5000

  });

  });

  < /script >

  < link href = "yoxview/yoxview.css" rel = "stylesheet" type = "text/css" > "

  <! - InstanceEndEditable - >

  < link href = "boilerplate.css" rel = "stylesheet" type = "text/css" > "

  < link href = "CSS/Layout.css" rel = "stylesheet" type = "text/css" > "

  < link rel = "stylesheet" href = "flexslider.css" type = "text/css" > "

  < link href = "css/flexnav.css" rel = "stylesheet" type = "text/css" / > "

  < style type = "text/css" >

  {body

  background-color: #E9E9E9;

  }

  < / style >

  < style >

  footer

  {

  min-height: 80px;

  Background: #000;

  border-top-width: 2px;

  border-top-style: solid;

  border-bottom-color: #C7E003;

  }

  < / style >

  " <!-< script src =" https://AJAX.googleapis.com/AJAX/libs/jQuery/1.9.0/jQuery.min.js "> < / script >-> '.

  < script src = "jquery.min.js" > < / script >

  < script src = "jquery.flexslider.js" > < / script >

  <!-Place in the head <>, after that three links-->

  < script type = "text/javascript" charset = "utf-8" >

  {$(window) .load (function ()}

  $('.flexslider').flexslider ();

  });

  < /script >

  <!--

  To learn more about the conditional comments around the HTML at the top of the file:

  paulirish.com/2008/conditional-stylesheets-vs-CSS-hacks-answer-neither/

  Follow these steps if you are using your customized version of modernizr (http://www.modernizr.com/):

  * Insert the link to your js here

  * remove the link below for the html5shiv

  * Add the class "No. - js' to the above html tags

  * You can also remove the link to respond.min.js if you included in your version of modernizr Polyfill MQ

  ->

  <!-[if lt IE 9] >

  "< script src="//html5shiv.googlecode.com/svn/trunk/html5.js "> < / script >

  <! [endif]-->

  <!-[if lt IE 9] >

  < link href = "IE - only.css" rel = "stylesheet" type = "text/css" >

  <! [endif]-->

  < script src = "respond.min.js" > < / script >

  <!-InstanceBeginEditable name = "head"->

  <! - InstanceEndEditable - >

  < / head >

  < body >

  < div class = "gridContainer clearfix" >

  < div id = "LayoutDiv1" > < img src="SJV-Images/Banners/LimeGreenheader-new-curved.png"/ > < / div >

  < div id = "Nav" >

  < div class = "menu-button" > Navigation < / div >

  < nav >

  < ul-point to stop "800" = class = "flexnav" >

  < li > < a href = "" > < /a > home

  <!-< ul >

  < li > < a href = "#content" > Sub point 1 1 < /a > < /li >

  < li > < a href = "" > Sub 1 point 2 < /a > < /li >

  < li > < a href = "" > Sub 1 point 3 < /a > < /li >

  < li > < a href = "" > Sub 1 point 4 < /a > < /li >

  < /ul >-->

  < /li >

  < li > < a href = "" > < /a > profiles

  < ul >

  < li > < a href = "" > Sub 1 point 1 < /a > < /li >

  < li > < a href = "" > Sub 1 point 2 < /a >

  < ul >

  < li > < a href = "" > Sub 2 point 1 < /a > < /li >

  < li > < a href = "" > Sub 2 point 2 < /a > < /li >

  < li > < a href = "" > Sub 2 point 3 < /a > < /li >

  < /ul >

  < /li >

  < li > < a href = "" > Sub 1 point 3 < /a >

  < ul >

  < li > < a href = "" > Sub 2 point 1 < /a > < /li >

  < li > < a href = "" > Sub 2 point 2 < /a >

  < ul >

  < li > < a href = "" > Sub 3 point 1 < /a > < /li >

  < li > < a href = "" > Sub 3 point 2 < /a > < /li >

  < li > < a href = "" > Sub 3 point 3 < /a > < /li >

  < /ul >

  < /li >

  < /ul >

  < /li >

  < /ul >

  < /li >

  < li > < a href = "" > < /a > photo library

  <!-< ul >

  < li > < a href = "" > Sub 1 point 1 < /a > < /li >

  < li > < a href = "" > Sub 1 point 2 < /a > < /li >

  < li > < a href = "" > Sub 1 point 3 < /a > < /li >

  < /ul >-->

  < /li >

  < li > < a href = "" > < /a > Alumni

  <!-< ul >

  < li > < a href = "" > Sub 1 point 1 < /a > < /li >

  < li > < a href = "" > Sub 1 point 2 < /a > < /li >

  < li > < a href = "" > Sub 1 point 3 < /a > < /li >

  < /ul >-->

  < /li >

  < li > < a href = "" > contact us < /a >

  <!-< ul >

  < li > < a href = "" > Sub 1 point 1 < /a > < /li >

  < li > < a href = "" > Sub 1 point 2 < /a > < /li >

  < li > < a href = "" > Sub 1 point 3 < /a > < /li >

  < /ul >-->

  < /li >

  < /ul >

  < / nav >

  < / div > <!-end = 'Nav'-> div id

  < div id = "LayoutDiv2" >

  <!-InstanceBeginEditable name = "Sacristy-Content"->

  <!-< script >

  If (Galleria) {$("body").text ("Galleria works")}

  < /script >->

  < div class = "yoxview" >

  Photo Gallery of < h3 > < / h3 >

  "" < a href="yoxview/Images-Yoxview/Trial_Gallery1.jpg" > < img src="yoxview/Images-Yoxview/Thumbnails/Trial_Gallery_thumb1.jpg"alt="First" width = "100" height = "97" title = "First image" / > < /a >

  "" < a href="yoxview/Images-Yoxview/Trial_Gallery2.jpg" > < img src="yoxview/Images-Yoxview/Thumbnails/Trial_Gallery_thumb2.jpg"alt="Second" width = "100" height = "97" title = "Second image" / > < /a >

  "" < a href="yoxview/Images-Yoxview/Trial_Gallery3.jpg" > < img src="yoxview/Images-Yoxview/Thumbnails/Trial_Gallery_thumb3.jpg" alt = "Third" width = "100" height = "97" title = "Third Image" / > < / has > "

  <!-< img src = "photo1.jpg" >

  < img src = "photo2.jpg" >

  < img src = "photo3.jpg" > - >

  < / div >

  <!-< script >

  Galleria.loadTheme('galleria/themes/classic/galleria.classic.min.js');

  Galleria.Run ('#galleria');

  < /script >->

  <! - InstanceEndEditable - >

  < / div >

  <!--

  < div id = "footer" > This is the content of the div layout 'footer' < / div >-->

  < / div >

  footer <>< / footer >

  "< script type =" text/javascript"src="js/jquery.flexnav.min.js "> < / script >

  < script type = "text/javascript" > $(".flexnav").flexNav ({"animationSpeed": 150}); < /script >

  < / body >

  <! - InstanceEnd - > < / html >

  The plug-in works. But I want to increase the height of the div with the class = yoxview. But I could not find this class. Here's the css.

  / * File of YoxView v2.0 CSS * /.

  #yoxview .yoxview_bottom {bottom: 0 ;}}

  #yoxview .yoxview_right {float: right ;}}

  #yoxview .yoxview_left {float: left ;}}

  #yoxview_popupWrap

  {

  position: fixed;

  top: 0;

  left: 0;

  Width: 100%;

  height: 100%;

  display: none;

  z-index: 100;

  }

  #yoxview

  {

  position: absolute;

  do-family: Arial, Sans-Serif;

  z index: 999;

  border: 1px solid #999;

  overflow: hidden;

  do-size: 10pt;

  text-align: left;

  max height: 1000px;

  }

  #yoxview an img, #yoxview_infoPanel an img {border: none ;}}

  #yoxview a: focus {outline: none ;}}

  #yoxview div.yoxview_imgPanel {position: absolute; top: 0; left: 0 ;}}

  #yoxview div.yoxview_mediaPanel

  {

  position: absolute;

  Background: #191919;

  Width: 100%;

  height: 100%

  }

  #yoxview .yoxview_ctlBtn

  {

  position: absolute;

  z index: 3;

  display: block;

  text-decoration: none;

  outline: none;

  Width: 50%;

  height: 100%;

  }

  #yoxview .yoxview_ctlBtn img

  {

  position: absolute;

  border: none;

  top: 50%;

  margin-top:-22px;

  }

  #yoxview a.yoxview_ctlBtn:focus, #yoxview a.yoxview_ctlBtn: active {outline: none; outline: none ;}}

  #yoxview .yoxview_notification

  {

  Width: 59px;

  height: 59px;

  position: absolute;

  top: 50%;

  left: 50%;

  margin-top:-30px;

  left margin:-30px;

  z index: 4;

  opacity: 0.6;

  filter: alpha (opacity = 60);

  background-image: url(images/sprites.png);

  background-repeat: no-repeat;

  display: none;

  }

  IMG #yoxview #yoxview_ajaxLoader

  {

  Padding: 13px;

  }

  #yoxview .yoxview_popupBarPanel

  {

  position: absolute;

  z index: 4;

  min-height: 70px;

  Width: 100%;

  right: 0;

  }

  #yoxview #yoxview_menuPanel

  {

  Width: 145px;

  height: 42px;

  padding-top: 0px;

  padding-right: 9px;

  position: absolute;

  right: 0;

  background: url(images/sprites.png) no-repeat left - 77px;

  background: rgba (0, 0, 0, 0.8);

  -moz-border-radius: 0 0 0 15px;

  -webkit-border-radius: 0 0 0 15px;

  border-radius: 0 0 0 15px;

  top:-42px;

  }

  #yoxview #yoxview_menuPanel a

  {

  display: block;

  Width: 45px;

  float: right;

  text-align: center;

  do-size: 0.8em;

  position: relative;

  margin-top:-5px;

  padding-bottom: 13px;

  text-decoration: none;

  do-family: Arial, Sans-Serif;

  }

  #yoxview #yoxview_menuPanel a duration of {color: white; display: block; margin-bottom: 3px;}  }

  #yoxview #yoxview_menuPanel a.last {margin left: 0 ;}}

  #yoxview #yoxview_menuPanel a: focus {outline: none ;}}

  #yoxview_infoPanel

  {

  position: absolute;

  bottom: 0;

  Width: 100%;

  height: 0;

  color: white;

  z-index: 2;

  overflow: hidden;

  }

  #yoxview_infoPanel #yoxview_infoPanelBack

  {

  position: absolute;

  Width: 100%;

  height: 100%;

  z-index: 1;

  left: 0;

  top: 0;

  }

  #yoxview_infoPanel #yoxview_infoPanelContent

  {

  position: absolute;

  Width: 100%;

  z-index: 2;

  top: 0;

  left: 0;

  }

  #yoxview_infoPanel span #yoxview_count

  {

  display: block;

  Width: 55px;

  do-size: 0.8em;

  float: left;

  text-align: center;

  padding-top: 8px;

  color: #bbb;

  }

  #yoxview_infoPanel #yoxview_infoText

  {

  margin: 0 55px;

  do-size: 12pt;

  padding: 5px 0;

  }

  #yoxview_infoPanel #yoxview_infoText #yoxview_infoTextDescription

  {

  margin-top: 1em;

  do-size: 10pt;

  padding-bottom: 0.5em;

  max height: 200px;

  overflow: auto;

  padding-right: 10px;

  }

  #yoxview_infoPanel #yoxview_infoText's .yoxview_error #yoxview a {color: #a7d557; text-decoration: none; outline: none ;}}

  #yoxview_infoPanel #yoxview_infoText a: hover, #yoxview .yoxview_error a: hover {color: #d5eeaa}

  #yoxview_infoPanel a.yoxviewInfoLink

  {

  display: none;

  opacity: 0.8;

  float: right;

  right margin: 5px;

  top of the margin: 5px;

  }

  #yoxview_infoPanel a.yoxviewInfoLink:hover {opacity: 1}

  #yoxview #yoxview_helpPanel

  {

  display: none;

  Width: 201px;

  height: 312px;

  position: absolute;

  top: 50%;

  left: 50%;

  margin-top:-171px;

  left margin:-111px;

  z-index: 5;

  color: white;

  padding: 20px;

  padding-top: 10px;

  cursor: pointer;

  }

  #yoxview #yoxview_helpPanel h1 {do-family: Arial Black, Arial, Sans-Serif; do-size: 1em ;}}

  #yoxview #yoxview_helpPanel p {margin-top: 80px ;}}

  #yoxview #yoxview_helpPanel #yoxview_closeHelp span {display: block; position: absolute; low: 20px; left: 0; text-align: center; width: 100% ;}}

  #yoxview .yoxview_error

  {

  display: block;

  text-align: center;

  color: white;

  do-family: Arial, Sans-Serif;

  do-size: 14pt;

  high: 41%;

  Width: 100%;

  height: 20%;

  position: absolute;

  padding: 10px;

  }

  #yoxview .yoxview_error .errorUrl {do-size: 10pt ;}}

  #yoxview .yoxview_top {top: 0; width: 50% ;}}

  #yoxview .yoxview_element {width: 100%; height: 100%; position: absolute;}  border: none; Background: #333; }

  . YoxView thumbnails one

  {

  float: left;

  margin: 4px;

  / * For the opacity of thumbnails: * /.

  opacity: 0.8;

  filter: alpha (opacity = 80);

  }

  . YoxView-thumbnails a: hover

  {

  / * For the opacity of thumbnails: * /.

  opacity: 1;

  filter: alpha (opacity = 100);

  }

  . YoxView-thumbnails by img

  {

  / * Set of white edges around the image, instead of the default blue browser: * /.

  border: 1px solid #ffffff;

  }

  . YoxView - photos-details {margin-bottom: 1em ;}}

  . YoxView-thumbnails-details h2 {margin-bottom: 0; padding: 0; do-size: 1.2em; make-weight: bold ;}}

  

  Where I could increase the height of the div? Pls help me.

  They asked to add a class = yoxview because the javascript that controls the Gallery is hard-coded to find all images under class = yoxview and then turn them into a gallery.

  If you want to increase your height DIV, you have 2 options:

  1. Add a new .yoxview class in your CSS (even if there is already a) and allows him to define a height
  2. Wrap your gallery in another DIV and assign height

  For the 2nd option, you don't have to touch the original yoxview.css. You can add to your CSS site. Something like this:

  {.gallerybox}

  min-height: 400px;

  }

  And your HTML code will become this:

  Photo Gallery