cstevensjr

Yes, I would be very interested in the bug tracker feature, but maybe as another site profile. I actually like this one just the way it is and have a few internal projects where I can use it. Thanks for the contribution.

I must admit that I immediately thought of Artisteer when I read the initial descriptions of this new product. I watched the videos and have to agree with Diogo that these are two separate products for two different markets. Artisteer produces unnecessarily bloated code where you can look at the generated code and know from whence it came. To be truthful, I've used Artisteer on Joomla and Wordpress sites. It's a workable templating system that gets the job done, however one great downside is that you are still tied to their Artisteer platform. The Macaw software looks interesting. I still believe that learning the PHP, CSS, HTML, MySQL and Jquery basics is the right way to go, Even if you use a visual tool later on, it pays to already know the essentials behind whatever you are using as a development platform and/or tool. I wish them the best. We need a variety of new development tools which should motivate the old guard to not sit on their laurels and not further innovate. Macaw seems like a step in the right direction. Only time will tell whether this is a flash or a fire.

For web development and support services, i only support the latest two versions of IE. Life is easier that way. .

I like this. The pictures seem to be very authentic which, to me, is very refreshing. Wish her good luck on this important endeavor.

@Craig A Rodway, you covered the essentials very good. The client/company should have in existence a written, well documented and enforceable Data Access Policy. This covers what are the approved or disapproved uses of the system. The policy would also state explicitly most of what Craig A Rodway has already written. A good system would have initial training on Data Access (Policy manual, Video Review, Classroom training) where the main points are gone over. You would have a signature of acceptance and provide either semi-annual or annual recertification of the user's acknowledgement of understanding the Data Access Policy. Where logging is concerned, there needs to be a policy where someone actually reviews the logs (to include a written certification of review). The same goes for testing the backup/restore process. It must be a valid and frequently tested system (to include a written certification of acceptable testing results). Make sure that users who use the system but also have backend administrative responsibilities, have separate accounts for each function. Setup alerts/alarms for certain critical administrative actions that report the action being taken. These alerts/alarms would go to the system administrator and other trusted individuals who are outside of the normal system administration realm. The system administrator needs to know the alert/alarm system is working, Someone other than the system administrator(s) needs to be aware of what critical changes are being made to the system This alleviates anyone gaming or deliberately sabotaging the system. Basically a good system is based on trust and adequate verification techniques. Good luck on your project because the human factor is the achilles heel of any information system.

Very nice, Thanks for working on this.

An awesome project! Great presentation and website.

I'm actually glad that ProcessWire has a lot of this type of safety features. This particular one has saved me many times. Sometimes I'm very bull headed about things. Even with a warning I would have deleted a template (because of course I know what I'm doing). Whenever I get that error, I have to stop and think "Oh yeah, I forgot about that" and then to proceed to delete the template where it won't affect what I have spent hours working on. I can't speak for everyone, but sometimes I think I'm smarter than I am. The safety feature makes me smile because I know that ProcessWire is a development platform that protects me from myself. Maybe there could be an option to turn off some of these safety features for anyone else. I just hope that one doesn't change anytime soon. As stated earlier, some of these suggestions have merit.

I read this over a few times and it seems to me that @wtrainer has not created the mySQL user and credentials prior to installing ProcessWire.

Changing passwords now is basically a gut reaction, a fear. This issue (the vulnerability) has been in existence for quite some time. Knowledgeable security individuals have known about this for some time. The fact that we (the public) are just now finding out about this means they now have a workable patchable solution. We all felt safe before we knew about this. The only thing that has changed so far is our knowledge of the vulnerability. We need to be reasonable and take a measured approach to our online security. You better believe this isn't the only vulnerability out there, it's just the latest we have found out about. If this wasn't related to an Open Source solution, we would still be in the dark, however we would feel secure. Not having the same password is a common sense practice. Security is not glamorous or fun. It takes an effort on the individual to make it work. Security is not profitable, so the corporations will not spend the money or time on it. Users want ease-of-use not complicated security policies. They only want security when the outside world touches them personally or financially. Don't get me wrong, this is very important and should be a wake up call to some. It's a constant reminder that we need to review and revamp our own personal security practices.

Why panic? We just should be aware and become knowledgeable about solutions. Until hosting providers and major websites identify and update their code, there's not much we can do about the situation. Changing passwords would be premature until the code is updated/verified and SSL certificates are reissued.

Thanks for all the Mac Software tips. I finally broke down and purchased my first Mac (iMac) today. Your suggestions are greatly appreciated.

http://www.lynda.com/

I've used both and pages is the best solution, in my opinion. As Macrura said, the Select AKA Dropdown is only for very simple and small amount of options. What anyone eventually learns is that using pages allows for future expansion, even when you initially think you will only ever need 4 or 5 options. My clients have always liked that they can add options to their fields whenever I use the page method.

https://processwire.com/talk/topic/1102-to-render-or-not-to-render-thats-the-question/

From your image, Drenthe is the first entry and it shows up as the default. If you want another location to be the default, move it to the top where Drenthe currently is. If there is something else you are trying to do, you have not adequately explained what it is that you want. It would be advantageous to you if you described exactly what you want and what you expect the result to be. "See attached image......" is not helping anyone help you. You have another topic https://processwire.com/talk/topic/5962-page-id-is-not-valid-for-field-name/ which, to me, seems related. A simple google search turned that one up and others.

Let me be a bit clearer - I believe this to be correct: If you assigned that field to a page and haven't added any pages to it, the field will look like it does in your image. Once you add pages, it will be as wide as whatever the title is of the longest named page.

Welcome to ProcessWire. I would look here first: https://processwire.com/talk/topic/3691-tutorial-a-quick-guide-to-processwire-for-those-transitioning-from-modx/ https://processwire.com/talk/topic/5221-case-study-significatojournalcom-migrating-from-modx-evolution-to-processwire/

If you are talking about the "municipal" field, my first question would be do you have any pages assigned to that field?

http://bit.ly/1iMfAIJ

Very nice.

Then they are surprised when you call them out on their technical inaccuracies.

Welcome to ProcessWire and please post for others what your solution was.

You are to be commended on a very nice website. I really like the colors and how the titles are displayed. Great job!

Pages are the easiest way to work with ProcessWire. You can even use Ryan's Import Pages from CSV module to help you create them.