dazzyweb

Thanks for that adrian. Would be cool to have that included as default with processwire. I noticed that there is an option Truncate Text. What is the purpose of this since the limit is already made with the max. characters and max words option. I can't seem to see what difference it makes ticking that option. Maybe I am missing something here.

Hi I am not sure if it is best to post here or general support but since i am still new to processwire I will post here. Is it not possible to limit the Maxlength in characters that are allowed in a field with a Type of 'textarea'? I see that this option is available if the field Type is 'text' but not if the field type is 'textarea'. Is there a reason for this?

Thanks for the info Pete Regarding the legal perspective as long as the licence and copyright is included with the code then all is fine such as is done with any other open source gpl code that most of us use at some point and of which processwire also uses which can be seen in the processwire copyright.txt with the list of of other code used with processwire and their respective copyright as I showed earlier. As said earlier this is how processwire deals with included open source licenced code it uses. For example under GPL it is quite common for software to be forked and the only requirement is that the copyright and licence stay intact somewhere within the code or files. Many gpl licenced cms have been forked and rebranded also. so legally I don't really see an issue with just having processwire and version in the admin as long as the licence and copyright files are included with the code. The reason I ask here about this is that I respect the wishes of Ryan even though legally anyone would be within their right to rebrand and customise the admin as they please under the freedom of the gpl licence as long as the licence and copyright files are included within the files of the cms. I agree with you that it is best to keep processwire name in clear view in the admin for the reasons you mentioned. I will look into the idea you mentioned of expanding the copyright line as you showed. Would be interesting to hear from Ryan his thoughts on this.

Thanks for that Pete.interesting. I do think that just the name processwire would make it look more professional. Just trying to think how it would look on wordpress with: 'Wordpress © 2013 Michel Valdrighi' Maybe I am moaning over nothing but the story biotech told resonated with me since i already had a similar response from a couple of people that I showed the admin to while playing around with processwire. (I was so excited i had to show someone ) Then reading that I can not change this or that if I want made me feel a little restricted since i thought i can customise the admin and frontend how I want as long as I keep the gpl licence and copyright intact with the code. I like to think i can mold a tool to how I need it for which ever purpose as long as I keep by the terms of licence. Anyway for best practice as Ryan said before I would always keep the name processwire and version in the admin.

Nice simple tutorial. Thanks

cstevensjr - I wasn't suggesting that you was creating a heated debate. What i meant is that I am a newbie here and that i don't want to create heat if you know what i mean as soon as I step inside the door. Nothing to do with you. I would just like to get down to the points i made. I feel that the points have not really being addressed.

Hi Firstly I am happy to have the name processwire and version in the admin as I said before but I was thinking just like the experience biotech had that it could be a problem. I asked a few others and they had the same opinion so I am not alone with this thinking. As well with all software that has gpl licence the person is attributed in the licence file or within the code just like has been done in the licence file included with processwire for code that has been taken from other sources which was also licenced under gpl as shown in the list below. Timepicker Addon - Copyright 2012 Trent Richardson TableSorter Plugin - Copyright 2008 Christian Bach Fancybox Plugin - Copyright © 2009 Janis Skarne Markdown Extra - Copyright © 2009 Michel Fortin SmartyPants - Copyright © 2006 Michel Fortin TinyMCE - Copyright © 2011 Moxiecode Systems Would you say that these people were not properly attributed by processwire since it is only included in the licence file? I really appreciate what Ryan has done and that is why I am writing here because I would really like to get my teeth into this cms as i find it very interesting. I am just used to using open source code and software and having the option to just include the licence and copyright with the code just like processwire does with other peoples code. "The creator of the product has the right to determine how their own creation works or is used/shared. Furthermore, the branding and copyright doesn't stop the proper functioning of the software." To answer the quote above, the creator has chosen to determine how the the works are used and shared under the gpl licence of which I am grateful for which is why I am here. Also the functionality is not the issue here. The issue is the freedom to customize the look of the software as is normal under gpl. I have only just come on the forum and don't really want to get into a heated debate over this. Just wanted to express my thoughts and give some feedback as a newbie here and the thoughts of others I have spoken to about this. I would be the first to recommend processwire to others and attribute Ryan for his work. I think that the perception and feedback from newbies or others looking at processwire for the first time is important and can help processwire further improve it's popularity. Many that come here for the first time are users of wordpress so will look at processwire the same way as wordpress since it uses the same licence and expect the same freedoms that wordpress provides under the gpl licence.

I am new to processwire and I am a little confused over what I can do with the admin since I didn't notice restrictions with other GPL software like wordpress regarding these things. I have the same question as biotech regarding having the name 'Ryan Cramer' next to Processwire.(Nothing against the name Ryan ) I can see how this can create issues and confuse the client. Also I didn't notice any other open source cms out there with a developer name or creators name next to the name of the cms in the admin backend. It kind of implies that the site was also designed by the developer of the cms. I am not sure that Ryan would like to take the credit for some badly put together or designed sites How about just having 'Processwire' and version as below like biotech suggested? Maybe in the next up coming version? ProcessWire 2.2.0 © 2012 Ryan Cramer vs. ProcessWire 2.2.0 © 2012 Other open source cms don't seem to have issues with this such as wordpress which even list on their plugin directory white label cms plugins (Didn't do wordpress any harm). Also Wordpress has no copyright notice at all in their admin. From what i see as long as the copyright notice and licence is distributed with the cms in the root folder and with the code then all is fine as far as the licence goes. I agree with Ryan that it is helpful to keep the name process wire and version shown somewhere in case of future issues and having it displayed in the admin can help but then again if there were future issues whoever could fix it would go into the files and see the software and version in the copyright.txt file included with the software. Personally I would keep the name and version in the admin as I think this is best practice for most cases. As a newbie to processwire I am very pleased with what I see and think that Ryan has done a great job but I am starting to feel a little restricted with what I can do with processwire after reading through the forum. I think that things like this can limit the growth of processwire if new comers to processwire feel they are not free to customise the software freely.

Thanks for the help and info. Really appreciated. apeisa. I feel the effects already

Hi Processiwre has attracted my interest and looks good so I'm am trying it out. I have a few of questions. What is the future of Processwire? I don't want to tempt fate but what if something happens to Ryan and he can no longer serve processwire. Would there be a future for processwire? Will processwire be further improved or will new improvements be payed for modules? I asked this as I see that there are payed modules for pro cache and form builder. Also are there any free form builder modules? Also if i purchase the processwire form builder for developer use, Can i still install it on sites after one year or am i locked in to yearly payment? Is there any difference between say the free WP Super Cache in wordpress and pro cache in processwire? Do modules developed for processwire come under gpl licence as well since processwire is gpl like how it is with wordpress? Just a few questions that are bugging me before I invest a lot of time trying out processwire. Thanks