apg1912

Thanks for the suggestions. I already have the menu in a short code but wanted to force it into the page header as opposed to the top of the page under the header where shortcodes can be added. I am using the OceanWP theme and so tried:

add_action(‘ocean_page_header’,’menu_function’);

This works to the point of inserting the ‘menu’ in the top left corner of the header and so I’ve re-located it using CSS. I’m just not sure whether this is a ‘recommended’ way of doing it or not.

• This reply was modified 5 years, 9 months ago by apg1912.

After staring at this long enough, I finally saw the problem. I’d included the add_action call WITHIN the function it was actually calling. Doh!

Phil,

Many thanks for the reply and explanation. I did try putting that column into the csv file but it didn’t seem to work in that the default values were not set when I looked at the imported data. However, I may have made a mistake of some sort and so I shall experiment further with it.

thanks

Exactly my point. You’ll see there is no ‘Attribute 1 default’ which is the one I’m asking about. Without it, you have to manually go to each added product to set it. A lot of time if you have many products.

For example, you set Attribute 1 (color) values to ‘Red, Green, Blue’, but want it to default to displaying ‘Blue’ as opposed to ‘Select an option’. This can be set manually, but it would be so much nicer if it could be set during the import process which that page I referenced in the first post claimed that you could.

• This reply was modified 5 years, 10 months ago by apg1912.
• This reply was modified 5 years, 10 months ago by apg1912.
• This reply was modified 5 years, 10 months ago by apg1912.

Phil, that is just what I did and based my sample data on. However, there is no field for ‘Attribute 1 default’ which is what leads me to believe it has been removed for whatever reason, which would be a shame

• This reply was modified 5 years, 10 months ago by apg1912.

I have solved this now. I had specified my test product as ‘variation’ rather than ‘variable’.

I am also having a problem with this. Worked fine on the release I downloaded a couple of months ago, but now I’m using 2.0 it does not work at all. I can’t understand how such an obvious piece of functionality can get through testing and not work on release.