EasyPopulate 4.0 Support Thread

[g2ktcf]

Just FYI, I was having similar issues to the previous poster in regards to the language import settings. After going back over the previous threads and changing the Import Language Override: language_id, everything started working fine.

Thanks!

[mc12345678]

Just FYI, I was having similar issues to the previous poster in regards to the language import settings. After going back over the previous threads and changing the Import Language Override: language_id, everything started working fine.

Thanks!

I've come to the mind that I am going to be establishing in new installs that language_id_only will be the default. The upgrade to 4.0.38 will *not* change the setting from those using 4.0.37.13, but the text about what *is* the default will change.

So the reason? Well, while adding capability and functionality is an improvement, there are too many that have already established their process. It may/may not include a column of text that uses or has a field that follows the language_code format (_en), but I'd rather this capability be considered a "secret" feature than a store's problem.

Another that has adapted/added to EP4 in support of the book product type had previously suggested that this feature just should not exist. At the same time I have seen and experienced the confusion that can exist by use of the database driven language_id instead of the international use of the language_code. But, in the improvement of the software, it is/was a feature seen as needed. Unfortunately I completely botched the default settings... I THOUGHT they were set right, but I was abhorrently wrong. I did also consider making a single switch that controlled both import and export together, but that to me seemed too restrictive and prone to its own issues.

And, while not addressed recently. One should consider that if an issue wasn't readily identified in the past that perhaps the issue is only from a recent change and often, I would say that a problem experienced "now" with the latest software is either directly because of the latest change or perhaps was not made known as an issue in the past... meaning, search of the posts beyond the latest release is not (or should not?) likely reveal assistance on those issues sought. That is if the issue is with the expected "normal" operation.

Hopefully now that the import/export discrepancy has been described at least three different ways, that until 4.0.38 or newer is installed over 4.0.37.13 that the situation can be more clearly understood/corrected.