EasyPopulate 4.0 Support Thread

[smpaulsen]

Good morning, and thank you for the reply / questions.

In short, the way we have ZC configured on the (shared) server means that we have to use the shared certificate. As such, the unsecure activity can take place at shop.mydomain.com, but the secured transactions need to go through secure.hostingservice.com/~username/shopname. Yes, feel free to point out all the ways this contradicts best practices. For the present, it is what we are doing.

Secondly, I misread the part about the temp folder being in the admin directory. That will cause some of the problems I was having. Thank you for pointing that out to me. I will test with the golden code and proper directory location.

That's all I've got. Let me know if you have more questions.

Again.... THANK YOU for maintaining such a useful tool.
~ Steve

[mc12345678]

Good morning, and thank you for the reply / questions.

In short, the way we have ZC configured on the (shared) server means that we have to use the shared certificate. As such, the unsecure activity can take place at shop.mydomain.com, but the secured transactions need to go through secure.hostingservice.com/~username/shopname. Yes, feel free to point out all the ways this contradicts best practices. For the present, it is what we are doing.

Secondly, I misread the part about the temp folder being in the admin directory. That will cause some of the problems I was having. Thank you for pointing that out to me. I will test with the golden code and proper directory location.

That's all I've got. Let me know if you have more questions.

Again.... THANK YOU for maintaining such a useful tool.
~ Steve

No, I get it. Recommendation in this situation of using the shared server's SSL certificate is to ensure that the DIR_WS_CATALOG and the DIR_WS_HTTPS_CATALOG be the same. In your situation that would be both being '/', therefore your HTTPS_SERVER would need to be: https://secure.hostingservice.com/~username/shopname
Where your HTTP_SERVER would be http://shop.mydomain.com

That should resolve any 'folder doesn't exist' condition. Otherwise, you may also run into problems with other plugins as well. (Will still look to see how this plugin compares to others in this regards and what if any changes need to be made.) :)

[greatgear]

I am new(er) to EP4 and to ZenCart in general...but I have been trying to get map_enabled and map_pricing to be included with the Model/Price/Qty export. I also have the MSRP addon installed...the MSRP field shows, but does not populate...the map fields are not in the export.
If I add the fields to the exported file, I can then update the file and upload it....all the fields import.
I am running version 1.5.4 of zencart and 4.0.28 - Beta 01-03-2015 of EP4
I also note in the FULL export (All products) that everything exports -
Any help/guidance would be much appreciated!
Mark

[mc12345678]

I am new(er) to EP4 and to ZenCart in general...but I have been trying to get map_enabled and map_pricing to be included with the Model/Price/Qty export. I also have the MSRP addon installed...the MSRP field shows, but does not populate...the map fields are not in the export.
If I add the fields to the exported file, I can then update the file and upload it....all the fields import.
I am running version 1.5.4 of zencart and 4.0.28 - Beta 01-03-2015 of EP4
I also note in the FULL export (All products) that everything exports -
Any help/guidance would be much appreciated!
Mark

Sorry for the somewhat delayed response. Saw the message earlier, but wanted to check into the code a little before responding. The MSRP module is recognized by EP4. The MAP module though is not. If the table that is modified by the MAP plugin is the products table, then the extra fields can be added in the admin, configuration, easy populate custom fields section. Typing in the field name(s) without v_ and each separated by a comma if more than one.

These custom fields will be exported using the full export. The msrp field products_msrp should be exported with the model/price/qty export option; however, I see that there was some aspects omitted/removed from the function file for export when using the model/price/qty export. Now whether that field is otherwise populated I couldn't say as I don't use either of the two plugins. Would need to see what else is to be done to export more with that option. I can't say that I see why MSRP data exports under one option but not the other.

Though it looks like the coding is a little modified/missing. I see that msrp is fully implemented for full export; however, there is only a partial implementation on the model/price/qty export.

It can be added in individually, though I plan on including/reintroducing it on the next update...

[greatgear]

Sorry for the somewhat delayed response. Saw the message earlier, but wanted to check into the code a little before responding. The MSRP module is recognized by EP4. The MAP module though is not. If the table that is modified by the MAP plugin is the products table, then the extra fields can be added in the admin, configuration, easy populate custom fields section. Typing in the field name(s) without v_ and each separated by a comma if more than one.

These custom fields will be exported using the full export. The msrp field products_msrp should be exported with the model/price/qty export option; however, I see that there was some aspects omitted/removed from the function file for export when using the model/price/qty export. Now whether that field is otherwise populated I couldn't say as I don't use either of the two plugins. Would need to see what else is to be done to export more with that option. I can't say that I see why MSRP data exports under one option but not the other.

Though it looks like the coding is a little modified/missing. I see that msrp is fully implemented for full export; however, there is only a partial implementation on the model/price/qty export.

It can be added in individually, though I plan on including/reintroducing it on the next update...

Thanks! That does answer a lot of the questions....I will keep watching for an update. I have devised a work around for the time - I add the fields before I update the file and it imports correctly.

This is a stellar tool!

Thanks again for the info and quick response!
Mark