Dynamic Price Updater

**Calljj** · 30 Aug 2018, 03:45 PM

Originally Posted by mc12345678

Possibly more to follow.

Thanks for looking.
moved the file across.
removed the comma from facebook pixel (although facebook was reading it fine through the Chrome Pixel addon checker thingy)
still no change.

**diamond1** · 13 Sep 2018, 02:18 PM

**mc12345678** · 13 Sep 2018, 02:26 PM

Well, this is expected behavior based on the code associated with ajax requested and as incorporated in ZC 1.5.6 (which has been incorporated into this version of DPU).

Essentially it has been determined that there is no value in indexing the ajax response.
(Especially when the response requires data to be posted )

**diamond1** · 13 Sep 2018, 02:39 PM

Well, so I can not use DPU anymore, or will it penalize me?

**mc12345678** · 13 Sep 2018, 04:17 PM

Originally Posted by diamond1

Well, so I can not use DPU anymore, or will it penalize me?

a 400 error as identified in RFC 2616 is identified as:

10.4.1 400 Bad Request

The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

I would say that response is appropriate for the information needed in order to provide an appropriate response. The Official Google Webmaster Blog discusses 404 errors, which this condition is not really the issue as the "page" exists, but nothing can be done by going to just that page, being authorized does not help. And from the other side, the server isn't exactly having a problem, but it doesn't know or can't process what was provided. On a "day-to-day" operation, this has no effect, but on someone trying to develop something, it can be discouraging if 400 is the response. :)

Basically, there should be no reason to stop using software that uses ajax style calls and identifies that crawlers shouldn't be concerned with the returned content. That is unless there is something specific being returned that is intended to be the content indexed... That is a different story and would have to be handled differently.

**lat9** · 13 Sep 2018, 04:59 PM

There's also this article (https://support.google.com/webmaster.../6062602?hl=en) that discusses how to block (i.e. exclude) URLs from being indexed by Google.

**diamond1** · 13 Sep 2018, 05:39 PM

Hello, the problem is not how to block the problem are all errors reported on google webmaster, I can not tell the bot google not follow the link and returning a 400 error damaging all the SEO. the ideal would have been a nofollow. Why did you do this? if the crawlers should not be interspersed with this you have to find another way that I think will damage the sites that are using DUP. Please find a solution to avoid making google angry.

**mc12345678** · 13 Sep 2018, 02:33 PM

Originally Posted by Calljj

Thanks for looking.
moved the file across.
removed the comma from facebook pixel (although facebook was reading it fine through the Chrome Pixel addon checker thingy)
still no change.

I still have not been able to reproduce this issue in a default store that has just DPU installed, regardless of tax included or not, without a change in base price nor with a special, a sale, or both.

**Calljj** · 15 Sep 2018, 10:37 AM

Originally Posted by mc12345678

I still have not been able to reproduce this issue in a default store that has just DPU installed, regardless of tax included or not, without a change in base price nor with a special, a sale, or both.

So can you just confirm for me.
1) you set up a product with zero value priced only by attributes.
2) you set up 3 attributes, priced at 10, 20, 30 (without the 'plus' sign infront in attribute manager).
3) you go to products price manager, and add a special price of "10%".
then on the website the original price (and of course sale price) changes when you select different atrributes?

I pretty confident it wont. I don;t think becuase of dpu, i think becuase of the way zen handles special prices, with products of zero value and priced by attributes.

for example, if you had everything setup as above, if you deleted the top attribute priced at 10, then the new attribute is assigned the sale price of the one deleted! This obviously then changes the overall disocunt on the new lowest attribute to be much more than intended!
original:

Click image for larger version.

Name: Untitled-1.jpg
Views: 86
Size: 18.5 KB
ID: 18030

10% discount:

Click image for larger version.

Name: Untitled-2.jpg
Views: 71
Size: 10.6 KB
ID: 18031

Because zen converts the "special price" discount to an actual numerical value. Then that value then becomes the minimum used for that product, no matter the attributes.
After deleting top attribute, price of second attribute gets changed to the value of the deleted one.

Click image for larger version.

Name: Untitled-3.jpg
Views: 71
Size: 8.5 KB
ID: 18032

You can see this, buy then adding the attributes back in again, using same values as deleted, and everything returns to normal once more.

Thread: Dynamic Price Updater

Thread Tools

Search Thread

Display

Hybrid View

Re: Dynamic Price Updater

Re: Dynamic Price Updater

Re: Dynamic Price Updater

Re: Dynamic Price Updater

Re: Dynamic Price Updater

Re: Dynamic Price Updater

Re: Dynamic Price Updater

Re: Dynamic Price Updater

Re: Dynamic Price Updater

Similar Threads

v151 Help with dynamic price updater

v139h Dynamic Price Updater 3.0 Help!

Dynamic Price Updater Error

Alternative to Dynamic Price Updater?

Dynamic Price Updater with href

Posting Permissions