-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
branch 4.039 fileset structure #70
Comments
The sub-folder For a pre-ZC 1.5.7 site, just using the base Regardless the installation method, the The temporary/storage directory though is still in relation to the store, not to specifically to the plugins directory. Development problems identified a few years ago is that while a version (e.g., If you have some suggestions on folder structure, feel free to offer. My next thought is to create a |
Yes, I assumed that, but then there are duplicated directories in the root
That's what surprised me, that the relevant files are not already in that directory. Incidentally, I did copy those files to the zc_plugins directory (and removed the ones in the main fileset) but EP does not appear in the list in the admin Plugin Manager. |
Understand, agree, and will seek to correct. In the interim, files in the "root" need to be placed in the appropriate location within the |
Yup. As I expected, files were "loaded" to the directory; however, had not been committed to the repo. Corrected by commit c244faa Next to move the files into a "clearer" yet still somewhat obscure |
|
Hmmm, there is still in the root: Installer which appear to be superfluous now. And, if EP can be installed by the Plugin Manager, the admin and includes folders can also go? And for me, any reference to ancient history like, pre-158. |
I see there are some minor issues with the install/uninstall via Plugin Manager to resolve for ZC200, otherwise ok. |
Just trying out the latest and greatest branch, but find this complex structure confusing:
Not an easy copy/merge!
I suspect some of these should be in zc_plugins...?
The text was updated successfully, but these errors were encountered: