#1 Re: Developer Help » Disable CMS overwriting template and module files » November 21, 2014 3:21pm

Oh ya,
When I installed it I needed to edit the ini file to allow short tags.

#2 Re: Developer Help » Disable CMS overwriting template and module files » November 21, 2014 3:18pm

I tried it a few times again today and couldn't replicate the error. I think I must have done something wrong the first couple of times

#3 Re: Developer Help » Disable CMS overwriting template and module files » November 21, 2014 11:25am

It just did for both module files and template files.
My Environment:

OS: Mac OSX 10.10.1
Web Server: Apache (Via AMPPS v4.5.4)
PHP: 5.4
MySQL: 5.6.17

BigtreeCMS: 4.1.3


I'll try it again later today to see if I can replicate it, or how to not replicate it. It didn't seem logical that it would overwrite existing files. I may be doing something wrong. If I find a true bug I'll fork the repo and send a merge request.

Thanks again

#4 Developer Help » Disable CMS overwriting template and module files » November 20, 2014 8:26pm

nate.lantz
Replies: 5

How can I disable the CMS from overwriting a template file?
I want to be able to create page templates locally, push them to a git repo, then set it up on a production server. I don't mind having to make the cms entry for a new page type in the developer settings, I just don't want it to change the files that already exist.

#6 Re: Feature Requests » Module Migrations » November 20, 2014 2:56pm

Ok thanks,

I missed that "Packages" part. I'll try to find the docs for it.

Again thank you for the quick response!

#7 Feature Requests » Module Migrations » November 20, 2014 2:33pm

nate.lantz
Replies: 4

Hi,

I just noticed something that has put my department in a slight halt when it comes to building modules. Normally we write all of the code for sites/applications locally, and then push our changes to a git repo. Then on our server(s) we pull the updated code from the repo (a little more to it but thats the basics). Everything is fine until we write code for a module due to the module builder in the CMS over writing the module files in the custom folder.
I was thinking that a migration task would be helpful in situations like this. For EX: build a new module locally (just the code), and then have a separate file for the migration that goes with it to setup the tables in the db.

I got the idea from other frameworks like laravel, cibonfire, Rails ...

On the CMS side there could be another option to import a new module instead of adding/building a new one.

Disclaimer, I am still new to Bigtree so if this functionality already exists please excuse me and let me know how to do it.



Thanks

Board footer

Powered by FluxBB

The Discussion Forum is not available on displays of this size.