diogo

You are already connected. The example I gave above and an understanding of the db structure are all you need.

You can create your own databases and execute queries easily with PW. Here is an example from Martijn that I found with a quick search (there are many more in the forums) http://processwire.com/talk/topic/4691-can-i-use-my-own-database-table-in-processwire/?p=45770 That said, I thinks it's proven already that PW can handle that amount of pages, and using them instead of custom tables would give you the benefit of being able to use the API of course. I guess I'm not exactly saying "what the hell man, just use pages!", but you need to find a balance between performance and how easy it will be to work with that data, knowing that performance will be also dependent on the system your site will live in and that there are cool tools like pro-cache that could help you with that.

I'm not an expert in this, but you can have a hidden field in that form with a random number or string generated with PHP only for the logged in user, store in in a session and check for it when the form is submitted. edit: in your case it's not a form, but you can still pass some info to the page, that can be sent back to server together with the file.

I read your question three times and still don't understand it, might be that someone else will read it more clearly and will be able to help you, but in case it's not just me having trouble with it, can you give some concrete examples of what you want to achieve?

Very nice! I like the profile pages in particular.

or you do it with javascript and wash your hands

Antti, you can create a normal template (with fields and a template file) for a custom page in the admin, and use $page, $pages, etc. instead of wire()

Not at all, don't worry about that

I agree that it's not difficult to create simple process modules, but I think it's great to be able to use normal templates in the admin. The idea of the module is that people don't have to change the way that they write code in pw or learn a new concept just to create a couple of backend pages. I do think that the module makes it easier to create admin pages (when it's working at least). I'll try to fix it as soon as I have some time. Edit: I didn't use the module for some time, but I did it now and I'm always amazed with how easy it is to create a custom page with it

In some cases Kimono might be overkill. If all you want is to extract some simple info from a webpage you can use an html parser. Here's an example using http://simplehtmldom.sourceforge.net/ <?php include "simple_html_dom.php"; $html = file_get_html('http://www.wunderground.com/cgi-bin/findweather/hdfForecast?query=porto,+portugal'); $location = $html->getElementById('#locationName')->plaintext; $temperature = $html->getElementById('#rapidtemp')->find('.b')[0]->plaintext; echo "Temperature in {$location} is {$temperature} °C"; //echoes "Temperature in Porto, Portugal is 22 °C" (that should make most of you jealous )

He'll choose Craft, everyone go home, there's nothing to see here

Sorry guys. I still didn't have time to address this problem. Don't really know how to actually...

If this is your ideal structure, there's no need to change only because of the frontend. There are many ways to make the frontend adapt to the structure. One would ve in the htaccess file, others can be done in the templates themselves. Simplest way would have to have simply: $session->redirect($page->child->url);, this would redirect the "core" to it's first child, the "home". The problem with this approach is that you would have "site.com/home" as the url of your home page instead of simply "site.com", the advantages are that you would have a very easy to create navigation and a one-to-one relation between the backend and the frontend. Another approach would be to render "home" from the "core" url, by putting this code on the "core" template: $page->child->render();, and excluding "home" from lists and searches: "settings > hide". Advantage -> you keep "site.com" as your main url, disadvantage -> you alter the structure and home is not searchable anymore without explicitly including it on find() searches. Edit: to make it clear, I agree with what Pete says below. My suggestions are only for the case you really want to keep that structure.

It's a grey area ethically. We also don't credit all the jQuery plugins we use, so I'm not sure we can criticize. That said, a template will always look like a template, no matter what you do with it it will always feel like one and not adapt completely to the product and the content of the website. Sometimes it will even impose a structure that doesn't adapt at all to what the client has to say to his audience. That's where you will have to mark the difference, making your websites feel completely adapted to the message of your clients. Potencially good clients —people that really care— will be able to evaluate your work when compared to something like that, and will choose you instead.

There's also https://www.insynchq.com/ for google drive.

We have this already http://modules.processwire.com/modules/service-pages/

Marty, the problem in this case is that both computers have to be on at a certain point.

Glad it's solved

I use this and has been working well. edit: not a huge fan of dropbox anyway, though I don't know why...

If all you want is to comply to baidu suggestion, just make a responsive site in abc.ext and point m.abc.ext to it like you probably did with www.abc.ext

4. I am a end user

It is a nice concept but you can achieve more or less the same with dropbox with symlinks. Just put a symlink of any folder inside the dropbox folder, and dropbox will happily let itself fooled.

For me this is the fastest way: 3 divs inside another: float them left, set box-sizing: border-box, and then give them approximately 1/3 of 100% width. give them an approximate right-margin that fills the blanks and 0 right-margin to the last div using :last-child. Adjust the right margin until the last div touches the side. http://codepen.io/anon/pen/xBGej

------------------------------------------------------------------------- | overflow visible | | -------------------------------------------- --------------------- | | | float left | | | | | | ------------------ ------------------ | | | | | | | | | | | | | | | | | float left | | float right | | | float right | | | | | | | | | | | | | | ------------------ ------------------ | | | | | -------------------------------------------- --------------------- | -------------------------------------------------------------------------

Alex, just noticed that you didn't have a proper welcome on your first post. So, welcome