diogo
-
Posts
4,296 -
Joined
-
Last visited
-
Days Won
79
Everything posted by diogo
-
nice soma! it's more practical like this.
-
You're right. Recently I re-installed the OS and didn't change the default font on chrome... doh! It's all working fine, I get my monospaced font and I prefer it like this, with no radio buttons...
-
I still get courier on chrome after cleaning the cache (!?) But now it's smaller if i choose monospace and bigger if i choose courier edit: But i can see you are making some changes. It's different everytime I refresh edit2: Actually, I think this choice only adds one layer of complexity. Isn't it better to just decide on a good font stack?
-
It works on firefox! it was cached on google chrome maybe... Sorry for that
-
hm, something must be wrong with the fonts, my default monospace font is dejavu, but i still get courier...
-
great soma!! edit: courier is not that readable with these colors, at least in my screen. would you consider changing it to "monospace, courier;". Since this is aimed at developers i bet everyone has a favorite monospace as default in their computer. Maybe it would ruin a bit your design though
-
if you don't find someone, why don't you choose a good company that you already know, and show them processwire. i'm sure they would learn it to win the work.
-
this would be great. what about having n site folders, and having the configuration file to direct each of them to the correct url and database?
-
I think that often people think PW is a lot more complex than it is, perhaps because it's approach is so different from something like Drupal or WordPress. In reality, when you know PW, things like Drupal and WordPress will seem needlessly complex (my opinion at least) Ya, this is how I feel exactly. The good thing about PW is that you don't need to learn lots of things. As soon as you learn the very basics, you can start building things by logic. The API is intuitive and works in a very semantical way. The grammar, on the other hand, is extremely simple
-
I think it's possible. It can take a while, but if you already designed sites, and are willing to make an effort and learn. Then you can Maruchan's answer can seem a bit scary, but he is right, for what it seems you will have to learn a lot. I'm also a noob on cms's, and even webdesigning, so, maybe I can try to give a less scary answer I guess your main doubt is mainly on how templates work. Putting it in a simple way, templates let you design several pages, writing the code only once. imagine that you have a very simple html, and all the pages on your website have the very same structure. <!doctype html> <html> <head> <title>my website</title> </head> <body> <h1>My Website</h1> <div id="sidebar"> "some code" </div> <div id="content"> "some code" </div> <div id="footer"> "some code" </div> </body> </html> What you would do to simplify your work is divide this code and put the parts that will be common to several pages in files that you can reuse. So, for instance, you can put this, on a file called 'head.inc' (i will use some dynamic content, like Maruchan explained) <!doctype html> <html> <head> <title><?php echo $page->title; ?></title> </head> <body> <h1><?php echo $page->title; ?></h1> <div id="sidebar"> "some code" </div> and this on another file called 'foot.inc' <div id="footer"> "some code" </div> </body> </html> you will be left with the content div that will go on a php file, for instance 'basic-page.php' that will call the previous pieces of code <?php include("./head.inc"); ?> <div id="content"> <?php echo $page->pagebody; ?> </div> <?php include("./foot.inc"); ?> On the backend interface, you will connect these template files with processwire templates, and assign fields to them: title like in <?php echo $page->title; ?> is one, and pagebody like in <?php echo $page->pagebody; ?> can be another (title is present on all templates by default, but page-body i just made up). after this you will create each of the pages of the website and assign them this template (or different ones that you can create). This was a very basic explanation. Hope it wasn't too simplistic... there's much more complexity than this, next step could be linking to stylesheets and creating dynamic menus for instance. Best thing you can do is play with the default installation. Open all the pages, create new fields and assign them to templates in the backend interface, and then, go to your template files and call them like this <?php echo $page->yourfield; ?>. Also have a look at all the templates that come in the default website. And of course, read the documentation http://processwire.com/api/ If you want to go the quick and easy way (but not as satisfying), you can also check these: http://www.lightcms.com/ http://pagelime.com/ http://unify.unitinteractive.com/ http://www.cushycms.com/ http://grabaperch.com/
-
it's a bit strange to see a website made with the default template, but this is because i'm looking at it all the time. People that will visit the website won't have the same feeling, of course. I would remove the skyscrapers on the top because they don't have anything to do with the subject, and also put some more images, since this website is aimed at people that don't know the place. edit: this shows that there is already demand for profiles in pw
-
Thanks a lot vknt sounds like a good choice. I will finish my subscribing process, and after I will try your code. From where do you call this file?
-
Soma, I used markdown on a website, and the client loved it and got the hang of it very quickly. I'm a Print Designer, and in the office I was even considering of making some kind of custom application with markup, so people could submit their tests to me instead of word or rtf documents. I tried to teach everyone to use styles in word, but people just seem to not understand the concept, and they ruin all the layout, and make it very tedious to correct everything... I agree with Martin, that it's good that editors are aware of the structure they are creating instead of relying on the visual thing. edit 1: Maruchan, nice! I will bookmark that one edit 2: For markdown there is this live preview http://softwaremaniacs.org/playground/showdown-highlight
-
Thanks again Apeisa. I will add this one to my list.
-
Thanks Apeisa! When configuring mailchimp it was annoying me that it was sending way to many confirmation and thank you emails for a simple email subscription, I designed and customized all the messages though. The reason why I gave up on from it, was that, apparently, you can't customize the error messages, and they are automatically translated and full of errors. I will try madmimi later. For now I'm quite happy with my efforts to collect the emails, here is what I have: <?php echo $pages->get(1011)->text; if($input->post->submit){ $email = $sanitizer->email($input->post->email); if(!$email) { echo "<p>" .$input->post->email . " is not a valid email</p>"; } elseif($pages->get("title=$email") instanceof NullPage) { $p = new Page(); $p->template = $templates->get("person"); $p->parent = $pages->get(1015); $p->title = $email; $p->save(); echo "<p>your email was saved </p>"; } else { echo "<p>" . $email . " exists already in our database</p>"; } } else { ?> <?php echo $pages->get(1011)->emailform; ?> <!-- Begin Signup Form --> <form action="<?php echo $page->url; ?>" method="post" id="signup"> <input type="text" name="email" class="email" id="email" /> <br /> <input type="submit" value="senden" name="submit" class="send" /> </form> <!--End signup form--> <?php }; ?> Besides this I'm validating the email with jquery before submiting. It's working, but am I doing something unsafe or it's ok?
-
I want to collect some emails with a very simple form (we want to collect only the email) for a future newsletter. I was configuring Mailchimp because i thought it would make things easier for me and the client... it doesn't. I could just collect the emails directly to the database, but since i'm building the site on PW i thought i could use it's powers to do it. The person that will manage this is not tech savvy at all, and would be nice to keep everything inside the admin area and using the same kind of logic. i thought of to ways: 1. creating users with the role guest (or equivalent, newsletter for instance) and a random password that won't be revealed to them. 2. creating a page "emails", with children pages where each one is an email. I would create this pages through the API every time the form is submitted. I'm tending for the second choice and the plan is: 1. collect the email from the input field. Sanitize it, and create a page with the email as title. The name of the page could be the email without the @ for instance. 2. confirm if the page is there with $pages->find("title=$email"). 3. if yes, display confirmation and email confirmation to the user using php mail(). this is only for collecting. I still have to think how i can make the newsletter also in PW. It makes sense to go this way? Or am I complicating?
-
I had to look up what FYI means, and I got all these: For Your Information For Your Interest For Your Inspection For Youth Initiative (Toronto, Ontario, Canada) Fiscal Year Information For Your Intonation (music) For You Indirectly Fresno Yosemite International, Fresno, CA (airport code) Forget You Idiot (polite form) i hope you don't mean the last one
-
Progress on ProcessWire 2.2 and overview of multi-language support
diogo replied to ryan's topic in Multi-Language Support
Great Peter! I think that Norwegian was missing -
I know that one, I was talking about en-ch, like in here: http://zueblin.ch/en-ch/#/investor-relations/ is that english-switzerland?
-
Very nice website Soma! Clear and easy to navigate. It looks good also! I'm curious, is the en-ch in the url on purpose?
-
If you say so, I believe it. But this was the feeling I got from your replies and review. The challenging tone of your writing did. I don't see your face or hear your voice tone, so, I might be also wrong here. I don't know if your enjoying this discussion or hating it. But I hope it will, at least, make you curious about PW and it's evolution. If you won't start using it, just come check it from time to time.
-
Thanks Pete, this is exactly what i meant
-
Nico, when people see the installer, they already decided to go through a process. I'm talking about something that tells them how easy it is. And also that gives other info, like permissions for instance.
-
Would be useful and encouraging for inexperienced users to put on the homepage some step-by-step instructions for installing PW.
-
Selfthinker, I don't think Ryan said you where impolite. He only stated that there's no point on taking this conversation further if you are not going to go deeper in the system. You are getting very extensive explanations from people that spent already lots of hours knowing and working with this system. Misunderstandings and lexical discussions apart, the truth is that at this point you are just ignoring most part of what people are saying and defending your initial thoughts without even trying to confirm if they are true (making your hands a little dirty in the system). The same way that you put these tools at test and give your opinions about them, you should also let other people give you their opinions about what you do, in these case your review (you linked to it here yourself, remember?). I understand that you don't have time to try all the products extensively, but the time it already took you to defend your review here, would be enough to at least work a bit on it and clarify some of your doubts, and, who knows, even help on some of the problems you have pointed out (build a non javascript admin theme, help with the multilanguage module, whatever...)
