Scenario: creating, designing, developing, a brand new, first time user, website installation:

> WP 3.0.4

> Atahualpa 3.6.4 theme


What, if any, "Fixes" ought to be applied, following brand new stand alone installation of ATA 3.6.4.

Many thanks.

check the 'New Version & Updates' forum

Originally Posted by juggledad

check the 'New Version & Updates' forum

I thought this was the New Version & Updates


My question is with regard to a brand new (or as in scenario - first user) installation of Atahualpa,

i.e. would not be updating, would simply download Atahualpa 3.6.4 upon WP 3.0.4.

What would be required?

Grateful thanks.

sorry, I wasn't looking at the forum this was in., Actually at this moment, (Feb 7, 2011) there are no bugfix's for 3.4.6

Originally Posted by juggledad

sorry, I wasn't looking at the forum this was in., Actually at this moment, (Feb 7, 2011) there are no bugfix's for 3.4.6

Thanks, Juggledad

so that being the case ... all should be well with brand new installation of 3.6.4 ... i.e. no issues with CSS Stylesheet ??

The reason I ask is due to my concern having looked at View > Page Source ... excerpt as follows:


<style type="text/css">/* ------------------------------------------------------------------
---------- BASE LAYOUT ----------------------------------------------
------------------------------------------------------------------ */

body {
text-align: center; /* centering the page container,
text-align will be reset to left
inside the container */
margin: 0;
padding: 0;
font-family: verdana, arial, sans-serif;
font-size: 13px;
line-height: 1.4;
color: #000000;
background: #d5d5d5;
padding-top: 20px; padding-bottom: 20px; }

a:link, a:visited, a:active {
color: #365DA0;
font-weight: bold;
text-decoration: none;
}

a:hover {
color: #365DA0;
font-weight: bold;
text-decoration: underline;
}

ul, ol, dl, p, h1, h2, h3, h4, h5, h6 {
margin-top: 10px;
margin-bottom: 10px;
padding-top: 0;
padding-bottom: 0;
}

/* remove margins on sub-lists */
ul ul, ul ol, ol ul, ol ol {
margin-top: 0;
margin-bottom: 0;


}
html:/* */not([lang*=""]) div.rMenu-center ul.rMenu li a:hover {
height: auto; /* reset for Netscape 7 and better */
}

/************************************************** *****************************
* HACKS : Suckerfish w/Form Field Support (for IE 5.5 & 6.x)
*
* IE6 and earlier do not support the :hover pseudoclass and so javascript is
* used to add the "sfhover" class of any LI element that the mouse is currently
* over. This method is called suckerfish and you can read up on it at:
* http://www.htmldog.com/articles/suckerfish/dropdowns/
*
* One problem with this approach is IE6 and earlier versions have a bug where
* form fields appear over the dropdown menus regardless of z-index values.
* The fix is to generate and stick an IFRAME element under the dropdown menus
* as they pop. The JavaScript used to do this requires that we hide menus off
* to the side of the screen ( left: -100000px; ), but normal rMenu operation
* is to hide menus with the DISPLAY property ( display: none; ). So also
* included in the set of rules below are rules to overwrite this original
* functionality of rMenu and utilize the LEFT property to move menus off-
* screen until needed. Any other rules that use the LEFT property in the
* normal rMenu system will also have to be ovewriten here as well. This
* includes the dropdown positions.
*
* NOTE: this allows for support of dropdown menus up to 3 levels deep. if you
* want to support greather menu depth you need to alter these selectors.
* read the above mentioned website for more info on how to do that.
*
* The fix to get dropdowns to appear over form fields requires we
* position menus off screen rather than simply hiding them with
* display:none. So you might think we should not be using the display
* property in the fields below. However we can because these display
* properties are only being set when a parent LI is being hovered, so
* the JavaScript used to operate on these LIs will already have the
* dimensions they need before these display rules are activated.
*/
* html ul.rMenu ul
{
display: block;
position: absolute; /* ovewrite original functionality of hiding
element so we can hide these off screen */
}
* html ul.rMenu ul,
* html ul.rMenu-hor ul,
* html ul.sub-menu ul,
* html ul.rMenu-ver ul,
* html ul.rMenu-vRight ul,
* html ul.rMenu-hRight ul.sub-menu ul,
* html ul.rMenu-hRight ul.rMenu-ver ul,
* html ul.rMenu-hRight ul

I am unaware of any issues besides the suhosin issue