I expect they both modify some of the same files, so will not be compatible without merging code.
Type: Posts; User: gjh42
I expect they both modify some of the same files, so will not be compatible without merging code.
Als, which attribute(s) are you wanting to be "required", and how are you setting that requirement? Does it work if you switch to the Classic template? Did it work before you installed Flexible...
What makes you think that this mod is what is causing your "attribute required" issue? Its code doesn't touch required status.
I had to alter a field in the database, don't remember exactly which one right now. I think I mentioned it in the readme...
Yep:
If you want to increase the length of Option Name comments...
You might. If you run into issues with different products, then it will be time to deal with it. No biggie, you would just need to make a p_###.css stylesheet for each applicable product (### = the...
Add to your stylesheet_flexible_attributes.css
#productAttributes {position: relative;}
#wAttrib-4 {position: relative; border: 1px solid #000000; padding: 0.8em; margin-top: 1em;}
#wAttrib-4>h3...
You can add a "comment" which will be output as a heading above any attribute, in stock Zen Cart (Option Name Manager, "edit" the option name after creating it). Flexible Attributes will let you...
Using actual <fieldset> elements would require a substantial amount of customized PHP coding to activate exactly at the right places.
Mimicking that effect is doable with stylesheet rules for the...
#wAttrib-14 .back {float: none; display: inline;}
#wAttrib-14 .back br {display: none;}
That's not enough information for me to answer. What product has attribute 14? I don't see it in the page you have been working on.
You want only the "whole pizza" column to be red, right? So make a rule just for that column:
#wAttrib-7 {color: red;}
You can adjust attribute sort orders in Option Name Manager if you want the "left side" on the left of "whole pizza".
You can give #wAttrib-7, #wAttrib-6 and #wAttrib-8 each width: 33%; and float: left; so they will sit side by side. You will probably need to limit the width of some sub-elements as well to make the...
The checkboxes are <input> elements within #wAttrib-7, and need different selectors to control them. I don't have time now to go into detail (probably won't until Monday), but you can use selectors...
You will have to adapt this to your particular attribute id (you can find it by looking at view source for the page), but something like this should work:
#wAttrib23 .attributesComments {position:...
You might need to use absolute positioning for the icon, along with some right padding for the text. I need to see it live to advise in more detail.
I don't think it can reasonably be done with styling changes (and work in various different circumstances), but it would be easy to permanently alter the order with a PHP file change. Find in...
That's tough to do in CSS without making them drop below the main product image, in which case they go all the way to the left under the image. This can do it, but I don't know of a way to make the...
You have the right settings, but something is making the colors take up too much width. Find this rule in your stylesheet
.attribImg {
margin: 0.3em 0;
width: 20%;
}and change it to...
You need to find the attribute id for Hemmed and use that in the rule. Your finished rule will look something like
#wAttrib-23 {
display: block;
} where the 23 is replaced by the attribute...
Yes, you can address attributes individually. For example, all attributes can be hidden with display: none; and the "Hemmed" attribute can be set to display: block; so it shows back up.
You had two copies of the stylesheet - stylesheet_flexible_attributes.css and stylesheet_flexible_attributes%20.css. The second one (the only one you have now) never got the original fixes and still...
You would need to add some code to a file as I mentioned in your other thread, to control the price as you want.
For the styling, replace these rules
#wAttrib-9, #wAttrib-10, #wAttrib-11,...
I'm not sure of the exact effects you want, but there are some errors in your CSS that you need to fix before you can style the attributes correctly.
#wAttrib-24 {
float: centered; ...
#wAttrib-9 h4.optionName, #wAttrib-10 h4.optionName, #wAttrib-11 h4.optionName, #wAttrib-12 h4.optionName, #wAttrib-550 h4.optionName, #wAttrib-777 h4.optionName, #wAttrib-15 h4.optionName,...
In your stylesheet_main.css, find this rule and add the part in red:
.navNextPrevWrapper {margin:12px 10px 30px 10px; padding:10px 0px; text-align:center; clear: both;}
The update was for a reason (I forget what at the moment), so use that one.
The two stock files that Flexible Attributes modifies have not changed since I wrote the mod, so it should work fine as is.
Thanks, Diva! I've seen info like this before, but this is a nice concentrated dose of it.
As far as I know, those are set by the browser and not changeable. I would be happy to be shown wrong:)
slingblade01 - You could probably add the "lbs." using the CSS :after pseudo-class, something like this:
#yourInputId:after {content: " lbs.";}
I would need to see your site to know the exact...
Neither of the two modified files in the mod package has changed in v1.5.0, so there should be no reason for it not to work.
Sorry, it takes javascript to make that kind of dependency, or custom PHP coding which would require a page refresh.
Check out the attributes.php file for a relevant example of this.
Find someone who is expert in MySQL to advise you on the selects you need;)
I know nothing about MS Access, but you could use SQL statements from Zen Cart files like...
In Attributes Controller, what do you have for each of the attributes in the orange box labeled Default Attribute to be Marked Selected:?
The demo stylesheet (stylesheet_flexible_attributes.css) ships with this rule:
h3#attribsOptionsText {display: none;}/*hide the "Please Choose:" heading*/ Comment it out if you want to keep the...
No, the attribute styling only applies to the product info page. Any other place attributes are displayed would need totally separate custom coding.
For the alignment, find this
stylesheet.css (line 277)
.wrapperAttribsOptions {
margin: 0.3em 0;
}
Change to
margin: 0 0 0.6em;
which puts all the margin at the bottom.
For the alignment, find this
stylesheet.css (line 277)
.wrapperAttribsOptions {
margin: 0.3em 0;
}
Change to
margin: 0 0 0.6em;
which puts all the margin at the bottom.
Try this:
#wAttrib-27 .attribsOptions>.back {height: 70px;}
Highlighting the label for a selected input may not be possible, but if it is, it will take some research. I'll see if I can dig up...
I like your solution of expanding the padding of the labels and giving them background images.
Since you do want the label text, only differently arranged, try substituting these two rules for the...
sports guy - Use this rule for hiding text as you describe:
#wAttrib-3 label, #wAttrib-5 label {display: none;} /*hide fraction text*/
A rule like this will put the text to the right of its...
Danielle - Yes, you can get that layout.
Set up the four headings as read-only attributes floated left, then the four right eye attributes floated left with the first one also clear:left;, then the...
I would copy the desired statement to replace the name statement for now:
if (PRODUCTS_OPTIONS_SORT_ORDER=='0') {
$options_order_by= ' order by...
Somehow there is a PRODUCTS_OPTIONS_SORT_ORDER constant that should be generated (or should be empty or '0' or null); if that is 0 then the correct sort order is used. If it has a nonzero value, then...
Oops, didn't see that the previous try at this post actually posted:)
The corresponding database field stores the products_options_sort_order value, but I'm not sure where the...
attributes.php sets the query sort order with this:
if ($pr_attr->fields['total'] > 0) {
if (PRODUCTS_OPTIONS_SORT_ORDER=='0') {
$options_order_by= '...
What is different about the environment in your localhost and live server? It pretty much has to be something there...
I'm not seeing anything wrong with your attributes settings or admin displays, but the storefront just ignores that sort order. Very weird.
I do note that there are missing defines in your admin...