Forums (Obsolete)

Member

oskar-grafiskhus - 1/16/2009 1:41:12 AM

Faster development with FTP

Hi there,

My company is starting to consider using Kentico as our primary e-shop cms. However, one of my biggest concerns is whether it's possible to use ftp when developing?

Say when editing css, if you have to edit it in the wysiwyg (god forbid), press save and so on - this can be a veeery annoying process.

Is it possible to edit these kinda files via ftp?


Kentico Support	kentico_jurajo - 1/16/2009 4:35:53 AM RE:Faster development with FTP Hi, When editing the CSS stylesheet in Site Manager -> Development -> CSS Style sheets you can check out the sheet into a file on disk. Then you can edit the file as you want to. After you are finished, you need to check in the file again in Site Manager. Best Regards, Juraj Ondrus

Member

oskar-grafiskhus - 1/18/2009 1:43:54 PM

RE:Faster development with FTP

Hi Juraj,

Thanks for the answer. The (big) problem with this is the check-in, which actually renders the function rather useless. Well, perhaps not useless but definitely not something that would improve my workflow, the way I had hoped.

What if you removed the check-in?

I assume you're a developer as well so you know how nice and fast it is to edit your file, press save, refresh your browser and see the changes immediately.

Kind regards,
Oskar


Kentico Support	kentico_jurajo - 1/19/2009 8:30:25 AM RE:Faster development with FTP Hi, Another option is to create folder under App_Themes with the stylesheet name and place all your sheets there and on the web site you need to link to this file on the disk to use appropriate styles. Best Regards, Juraj Ondrus

Member

Mufasa - 1/19/2009 4:44:05 PM

RE:Faster development with FTP

I personally just run an entire copy of my Kentico sites locally on my development machine. I make changes to the style sheet (and whatever else) on the development database. Once it's the way I want it, I copy & paste or FTP it up. Not the cleanest method, and non-existent source code control (for any changes in the database data anyway). But it works for one developer, who writes every changed file or object down. I wouldn't recommend this for anyone disorganized or in a team though.