EasyPopulate 4.0 Support Thread

[mc12345678]

Huh? That must have been the problem!




Because of what you just said, I typically remove any column I do not want modified, leaving only what I am changing, plus the control (model# being EP4 default). Since I wasn't changing product_name, I removed it.

But I just uploaded with product_name included (all fields, really) and it went in exactly as expected, removing the foul links.

Thanks, MC! You da man!

I'll take another look at that section of code. I think in the addition of languages/an extended field if found present in the database that the test for that sql to be run or not didn't get updated... It looks like originally that code section was intended only to address the products_name field and to be run only if a name was to be inserted or updated... Then along came some other fields... I expect to revise it to still do a test, but 1) only call the code section if something within is to be acted on and 2) only to include the field(s) with data to optimize the query as able.

[Feznizzle]

1) only call the code section if something within is to be acted on and 2) only to include the field(s) with data to optimize the query as able.

That seems so much more logical to me! First hit the index (model# being default), then check field. If the index supplies point of reference, no need to act on anything other than supplied fields.

Wait, maybe that's backwards? First check fields to find out what needs action (code needs calling), then apply only to indexed entry.

Having to supply the product name when all I wanted to do is alter product_url seemed illogical.

Anyway, glad your on it! Thanks again!