Custom fields not work after update to 3.0.18

[GJC Web Design]

these settings have no effect if there is over riding in templates/xxxx/html/com_virtuemart/

compare the code with the standard

[cvrak]

these settings have no effect if there is over riding in templates/xxxx/html/com_virtuemart/

compare the code with the standard

I can't find the com_virtuemart folder, see my attachment.
Located somewhere else? Some other error?
Thanks

[GJC Web Design]

looks like no over rides.. to confirm just add something to the  components\com_virtuemart\views\productdetails\tmpl\default.php and see if it appears

e.g. <!--I am the default-->

if that confirmed then you have another prob.. JS error etc?

[cvrak]

looks like no over rides.. to confirm just add something to the  components\com_virtuemart\views\productdetails\tmpl\default.php and see if it appears

e.g. <!--I am the default-->

if that confirmed then you have another prob.. JS error etc?

I've added
<?php
    echo "Hello";
?>
and is displayed at the product page .

What else can do?
Thanks

[GJC Web Design]

ok -- now

if that confirmed then you have another prob.. JS error etc?

[cvrak]

ok -- now

if that confirmed then you have another prob.. JS error etc?

Any suggestions about the JS error?

[GJC Web Design]

JS is on YOUR browser.. how could I?

use the search please!!!

e.g.
http://forum.virtuemart.net/index.php?topic=119638.0

[cvrak]

I used Firefox's Firebug and inspected the specific element (screen_03.jpg).
At the console I got some errors, one of then was "Use of getAttributeNode() is deprecated. Use getAttribute() instead" . I edited mootools-core.js, and changed the text, and the error is gone.

Now I get "Empty string passed to getElementById()" at .../media/jui/js/jquery-min.js:2:24932  (screen_04.jpg).

The strange thing is that at the site, custom fields are working properly, the problem is only at administrator UI.

Any suggestions, pls??

[Brockney]

I actually got the custom fields working by changing the 'Please Select' option to one of the options that are selectable.

So it gave me the option to choose either

Tropical Storm Burst - 30ml - 3mg
Tropical Storm Burst - 30ml - 6mg

However, whichever option was chosen, only Tropical Storm Burst - 30ml showed in the customer cart and no strength 3mg or 6mg

Here are the screenshots in order to show what I did. Is it possible to go back to a slightly previous version of Virtuemart until we figure this out?

[cvrak]

Hi,

Trying to find out how I can solve my problem, I've done the following:

1. I've installed VM 3.0.18 to another site (joomla version, template, etc are the same).
Using the Firebug's console I got the same 2 errors:
    Use of getAttributeNode() is deprecated. Use getAttribute() instead.    The file is media/system/js/mootools-core.js
    Empty string passed to getElementById().   The file is components/com_virtuemart/assets/js/jquery-min.js

The strange thing is that the custom fields dropdown menu (administration UI) is working ok.


2. At the problematic site, I've corrected the Use of getAttributeNode() is deprecated. Use getAttribute() instead error, but the problem remains.
    I've replaced the mootools-core.js & jquery-min.js from the working site, the problem remains.

3. Anotther strange thing is that if a product has already a custom field set and try to add another, the dropdown menu is working ok!! The problem appears only when I try to add a custom fields set for the first time.


I'm completely confused with this. Can anyone help??

Thanks
Chris

[cvrak]

Continue from my previous post:

I've replaced all folders & files from the 3.0.18 VM clean install package. The problem remains!!
Finally I've returned to 3.0.14 version and now its working!!

Can anyone explain this?

I believe VM team will deal with this issue for future updates.
Any suggestions/comments are more than welcome.

[Studio 42]

Hi cvrak,
i think that using vm 3.0.16.2 is safe. I have new problem too with VM 3.0.18, but not using vm 3.0.6.2(payment,shipments,customfields ...).
And with last Joomla too, because some internal changes in jommla 3.6.3+

[Brockney]

Message to GJC your description on page one seemed to solve the problem and many thanks 

For anybody who has missed it, here it is

look in your

\templates\xxxxxxxxx\html\com_virtuemart\productdetails\default.php if over ridden .. if not in the VM views

find the html container holding the whole code

normally something like

<div id="productdetails-view" class="productdetails-view productdetails">

change it to

<div id="productdetails-view" class="productdetails-view productdetails product-container">

[Milbo]

com_virtuemart.3.0.18.1_extract_first.zip has now a new option in the vm config, which can be enabled to use old layout overrides. I found the fallbacks, but they are only enabled, when the config option is activated.
http://dev.virtuemart.net/attachments/download/1029/com_virtuemart.3.0.18.3_extract_first.zip

Brockney, what you describe is the general Hint in https://virtuemart.net/news/latest-news/477-release-of-3-0-18-connecting-the-loose-ends

Important for shops with overrides

The new js for using ajax for reloading product content uses now always the same class. The class is "product-container". Just search for the div with "productdetails-view productdetails" and add "product-container". In case you want the ajax reload within a product modul, you need to adjust the overrides here also. Furthermore the layout login of the user view is now in the sublayout folder. Members who used the ajax for child variants within the browse view should change the layout back to default.

For a full list of all changes or more information how to adjust your overrides, please read here in our forum http://forum.virtuemart.net/index.php?topic=135402.0