non-encasulated plugins and installer directory
Hi,
I am in the process of porting my 1.5.6c zencart to 2.1.0, removing every possible.
I have a couple of critical custom plugins (multi language country and zone names) that are an integral part of my site. These do not exist any more and are not encapsulated. They use the admin/includes/installer directory. Since 1.5.7 the encapsulated plugin manager is available, but is it possible to keep using an admin/includes/installer directory (which does not exist in 2.1.0 out of the box) at least for the purposes of testing the plugin, before possibly attempting conversion to encapsulated version?
I don't even know if the installer is required any longer since the database will be copied, and the plugins' other files and file changes are being ported.
Re: non-encasulated plugins and installer directory
> is it possible to keep using an admin/includes/installer directory (which does not exist in 2.1.0 out of the box)
Yes. This directory was also added to 1.5.6, and it can be added to 2.1.0.
(As you noted, it may not even be required.)
Re: non-encasulated plugins and installer directory
Quote:
Originally Posted by
swguy
> is it possible to keep using an admin/includes/installer directory (which does not exist in 2.1.0 out of the box)
Yes. This directory was also added to 1.5.6, and it can be added to 2.1.0.
(As you noted, it may not even be required.)
That /admin/includes/installers directory was never part of a base Zen Cart distribution. There were a couple of plugins (SitemapXML comes to mind) that added that directory.
Re: non-encasulated plugins and installer directory
I see your v1.5.6c is modified for Japanese language.
You know there is a Japanese language pack for v2.1.0 that works very well. I maintain it and will be happy to help you if needed.
Re: non-encasulated plugins and installer directory
@swguy, @lat9, many thanks for your feedback. I understand now, that is good news.
@pilou2, thank you, yes, I have studied your excellent language pack, and am integrating it as much as I can given my initial setup (based on the "furigana needed" condition rather than "japanese language" condition from the old Japanese ZenCart code). Thank you for your offer of help. I do not want to confuse this thread with feature suggestions or feedback for your module, but here a shortlist:
- I have made the admin side multi-language as well.
- this includes things like multi-language tax rates which needed a new table.
- I have added an address language field for the address, which affects the choice of country and zone (i.e., addresses can be specified to be in English or in Japanese, independent of the language of the cart), and therefore I needed some new functions to dynamically update countries and zones dropdowns.
- I use separate country and zone tables with language and names, where country and zone names exist per language, plus the various ISO country and zone codes. I understand this part could potentially be handled by core ZenCart now, but there are still issues (but less customization required than previously because ZenCart has certain multi-language capability for countries and zones already).
On the other hand:
- I am using all the new Japanese postage (and payment) modules from your language pack, rather than attempting to port the existing ones from 1.5.6c.
- I am using your language packe to correct/expand language strings.
- I am using your language pack to note any minor code/style fixes.
I'll be happy to summarize in private or in your support thread once the porting is completed.
Re: non-encasulated plugins and installer directory
> That /admin/includes/installers directory was never part of a base Zen Cart distribution.
Sorry, re-reading my response made me realize this was confusing. The directory was added *by the plugin author* to 1.5.6 and you can add it too to 2.1.0.
As @lat9 notes, it was never included in any release of Zen Cart.