diogo

Hello Igor, you have lots of questions there. All that is doable with ProcessWire, and answered already to the most simple question: PW is not to heavy for shared hosting, it's even much lighter than most known CMSs. Because you have so many questions, I will answer with links. After reading those, you will be able to to narrow down your questions a bit so you can get some really useful answers: categories: http://processwire.com/talk/topic/3579-tutorial-approaches-to-categorising-site-content/ comments: There is a built in comment system (same as in PW site pages), you just have to activate t in modules: http://processwire.com/api/fieldtypes/comments/ eCommerce http://processwire.com/talk/topic/1732-shop-for-processwire-apeisa/ (lots of suggestions besides Apeisa's module) http://processwire.com/talk/topic/3756-shopify-integration/ (most recent discussion) Contact form: http://modules.processwire.com/modules/form-template-processor/ http://processwire.com/talk/topic/59-module-want-form-builder/#entry343 or http://store.di.net/products/processwire-form-builder group/permission http://processwire.com/api/user-access/roles/ multilanguage URLs http://processwire.com/talk/topic/2979-multi-language-page-names-urls/

Out of curiosity, does someone use netbeans as PHP IDE? How does it compare with PhpStorm? And also: Ryan, did you setup Vim for PHP (I mean, with code sniffing, unit test support, etc)?

You asked, I answered

Meanwhile I converted the Docs from the website in an ePub file. I know it's not really a book, and I confess that the conversion it's s bit clumsy, bute here it is for those that are interested https://docs.google.com/file/d/0B6RyV62pA8iwckthSTE1XzBOQzA/edit?usp=sharing

Still using textadept as my default editor here, but wanted to throw another editor that seems very solid to the discussion http://www.activestate.com/komodo-edit (trying it as I write).

Done, moved it Wishlist & Roadmap -- Just a detail, but maybe I would change the order in my second solution: $link = $page->urlfield || $page->pagefield->url;

I don't know if something like this is on the way, but I see two possible solutions. One is to have a text field that would serve for both (but you wouldn't have the url check ability, nor the page select interface) and do something like in the template or a process module: $link = is_numeric ($page->field) ? $pages->get($page->field)->url : $page->field; The other is to have both fields, page and ulr, on the template (maybe grouped under a fieldset) and write that only one will be used. On the template you would have something like: $link = $page->pagefield->url || $page->urlfield;

where to start? from out of my head: http://processwire.com/talk/topic/3265-fredi-friendly-frontend-editing/ http://processwire.com/talk/topic/3602-pw-online-installer-download-of-latest-pw-install-to-server/ http://processwire.com/talk/topic/3691-tutorial-a-quick-guide-to-processwire-for-those-transitioning-from-modx/ http://processwire.com/talk/topic/3745-hanna-code/ http://processwire.com/talk/topic/3474-admin-custom-pages-module/ and most importantly: http://processwire.com/talk/topic/3498-karena-savannah-cramer/

Went yesterday to the cinema to see "Drupal & Joomla 6", and was not disappointed. Highly recommended!

In this case it makes sense to show an alternative way of doing what Reno showed. Just to make it a bit closer to the TXP example: <ul> <?php foreach ($pages->find("template=skyscraper") as $s): ?> <li><a href='<?=$s->url?>'><?=$s->title?></a></li> <?php endforeach; ?> </ul>

yes

For me the best way is to leave the template without a file.

The file displayed is always index.php, but the content being rendered depends on the url. It's like when you have a query string, like in domain.com/index.php?field1=value1&field2=value2&field3=value3, in that case all those pairs field/value can be pulled by get, and the content displayed can vary depending on them. Except that here, normal URLS are redirected to index, and via the URL segments the right page is displayed via some PW magic. I don't know exactly how it works, but maybe someone more informed can explain the details.

and this http://devzone.zend.com/6/php-101-php-for-the-absolute-beginner/ edit: Fernando, there is already a spanish translation for the admin http://processwire.com/talk/topic/1003-spanish-es-es/

How come not? Works with me on every browser I tried...

@Harmster, he means the ID of the page from where render is called. @sakkoulas, you can use any of these techniques http://processwire.com/talk/topic/3660-what-page-was-the-caller-of-render/

When I go to that page, I get the default apache welcome page, is processwire installed on a subfolder? Edit: Oh, and welcome to the forums

You want it hardcoded or absolut? because they are different. You can have a dynamic absolute like this rtrim($config->urls->root, "/").$page->url; // rtrim removes the trailing slash from the root url or, if you really want it hardcoded (I can imagine you need it for javascript), you can view the page and copy the url, or just echo that code and copy the result

One way is to tell the client to reduce the images size. I think we shouldn't try to solve everything, and put a minimum of responsability on those that edit the website. Just indicate them an easy tool to install on their computer http://www.addictivetips.com/windows-tips/image-resizer-powertoy-clone-for-windows-7vista/

Great read Kongondo! Soma already pointed out the only problem I noticed.

This looks great Kongondo!! Although I don't know anything about MODX, I will read it tomorrow in the morning in my Kobo reader If someone else feels like, here is the ePub file that I created (Apparently I can't upload .epub files to the forum, so I'm sharing in Google Drive) https://docs.google.com/file/d/0B6RyV62pA8iwTm1BTnNOYmRYRDA/edit?usp=sharing

Hi, and welcome Judging by this sentence, I would say you are in the right place. Still, I would advise you to read Ryan's answer to this post to make a decision about building something like this with PW http://processwire.com/talk/topic/3549-can-i-build-my-project-using-processwire-events-ecommerce-trip-sharing-community/ About your concerns: Yes, the system can handle thousands of users/related pages/numbers of posts etc and it can be scaled up without problems. Scalability is one of the strong points of ProcessWire.

I'm in Germany this week, and noticed that grooveshark unlocker was discontinued. Here is a great alternative http://proxmate.dave.cx/

Study the cheatsheet, especially the $pages and Selectors parts http://cheatsheet.processwire.com/

Of course you can... $pages->get(page_ID)->name_of_field