Hi,

The cause for the not working “add to cart” is the “Beautiful Add to Cart PopUp Notification”. We’ve tried to make it compatible, but for the moment this is not possible.

Since this modification alter all themes templates, we recommend to modify it a bit, so it changes only the default theme, e.g. change this route:

catalog/view/theme/*/template/.....

to:

catalog/view/theme/default/template/

We are sorry for the late reply, but converting 3rd party is not part of the free support we offer. Although we always try to help everybody, there are issues that have greater priority.

BR,
ThemeBurn team

Hi,

There is a JS syntax error on the product page, that is introduced by template modification (it doesn’t matter whether this modification is made manually or by an extension).

Unfortunately, you will need to roll back the changes, you have made. The modification relies on some Bootstrap scripts that for the moment are not properly supported by the theme. That is why you cannot use it for the moment.

BR,
ThemeBurn team

Hi,

There is an error on your productpage. You can check with your browser, for example Developer Tools – Google Chrome.

Uncaught SyntaxError: Unexpected token } on black-1-3-gallon-can.html:1606

  timer = setInterval(function() {
      if ($('#form-upload input[name=\'file\']').val() != '') {
        clearInterval(timer);

        $.ajax({
            url: 'index.php?route=tool/upload',
            type: 'post',
            dataType: 'json',
            data: new FormData($('#form-upload')[0]),
            cache: false,
            contentType: false,
            processData: false,
            beforeSend: function() {
                $(node).after('<i class="fa fa-circle-o-notch fa-spin"></i>');
                $(node).attr('disabled', true);
            },
            success: function(json) {
                $('.text-danger').remove();
                $(node).next('.fa-spin').remove();
                $(node).attr('disabled', false);

                if (json['error']) {
                    $(node).parent().find('input').after('<div class="text-danger">' + json['error'] + '</div>');
                }
                if (json['success']) {
                    alert(json['success']);
                    $(node).parent().find('input').attr('value', json['code']);
                }
            },
            error: function(xhr, ajaxOptions, thrownError) {
                alert(thrownError + "\r\n" + xhr.statusText + "\r\n" + xhr.responseText);
            }
        });
      }
    }, 500);
});

Last line is incorrect.

• This reply was modified 2982 days ago by  ultimatia.

Yup I see that error in google dev console, but since the page is dynamic (and I’m not a real coder) I can’t for the life of me figure out where the unexpected token is actually coming from… and I cant find any info online about how to do so…

I do appreciate the help, and I’m sure others already do (or will be having) the same issue.

It seems if we could just figure out what file is actually causing the unexpected token we might solve the problem.

—–
btw: how can you say this?
“What we can say is that there is some code from the “Beautiful Add to Cart PopUp Notification” vqmod that is not placed correctly and break the add to cart function.”
If you can’t pinpoint it how can you say its having an effect?
If you can pinpoint it please tell me how.
—-

If you want I can give you access to the backend.

• This reply was modified 2982 days ago by  bigmoon.

OK Fixed it, crazy.. all I had to do was delete the file and it is fixed.

deleted > /system/storage/modification/catalog/view/theme/pavilion/template/product/product.tpl

close issues, tx.