elmago79

No idea what went wrong. Updated form 2.6.10 t0 2.6.12 and the problem went away.

This I guess is very simple but it is driving me a bit insane. I'm using this bit of code to populate the main page of a website. $pages->find('template=singleblogpost, sort=-fecha_de_publicacion')->eq(0); There are many kinds of pages, each with a different template. I have singleblogpost, singlegallery, quotations, adds, so I just change the template. And it works for every king of page except for the 'video' template. $pages->find('template=video, sort=-fecha_de_publicacion')->eq(0); Do you have any idea as to what am I doing wrong?

That worked! I have no idea what I did, but turning off the fingerprint worked. I can login without trouble

As I talked about elsewhere, I launched a processwire site: http://dgp.conaculta.gob.mx/dml2015 last friday. Something weird happened with the login process. I would be unable to login or would get logged out about 30 seconds after succesfully login in. At first, I thought that it was a permissions issue, and so I went ahead and chmod 777 the entire site folder just to see if this fixed things. It didn't. However, I managed to discover that I only have trouble with login on my office network. Form my house, or anywhere else, I can login without any problem. It is only at my office that I keep having trouble login in. So before I write to the sysadmin to explain what is my problem, perhaps you could throw me some pointers Maybe it is important to note the we login to various sites (Wordpress, custom) and is only this new processwire instalation that is giving us problems.

We needed to make a small site for World Book Day in my office and had officially no budget for it, so it sounded like a good pretext to try Processwire for the first time. So it took last year static site, hammered on some new colors and images and then processwired it. Here it is: http://dgp.conaculta.gob.mx/dml2015/ There are some things to fix in the frontend, and surely is nothing to be noteworthy as a site, but it will serve it's purpose. I was kind of surprised by the fact that the frontend is still taking way more time to do everything right than the backend. I had to learn a lot more php than I ever thought I would in my life, and my spaghetti code might be unreadable, but I managed to program and add all the dynamic content in about a day (and since receive changes almost daily, it's a blessing that we have a clear interface to edit it). The most impressive thing for me was that if I tried to do something, it usually worked. Since it's my first try, that was something I never expected. Also, you need to publicize and document the Page field a lot better. It is incredibly powerful. I know I'm only scraping the surface with this site, but my guess is that this feature is what made making content dynamic in this such an easy feat. However, I learned some things the hard way: * Never use a title field inside a find selector. If it has quotation marks or other special character it will fail completely. * You can't use the datetime filed to only write time --even if it seems you could--. This drove me crazy for a while, but then I discovered that about two weeks ago some kind soul created a module for a time field. Many blessing for that perfect timing. * Some places you can chain selectors, some places you cannot. I have no idea why. I mean, I know its php related, but I guess I need to dive in a lot deeper to get it. * Some things are case sensitive and some are not. Some things you have to always write in lower case. I'm still trying to get the hang of it. * Migrating to production it's a pain. You get a lot of unexpected errors, which thankfully the forums helped me solve. And two questions: * In order to restrict the kind of template the children of a page could use, I ended up creating another template who's only reason to exist was said restriction. Is there an easier way to do this? * I'm having some weird login problems. A user can't login or get's logged out after some minutes. How can I troubleshoot this?

Thanks for the answers. It actually is very simple! The file field seems like the thing I was looking for. As an extra, It used to drive me crazy that in Wordpress I had to load all this js to every page that I was just going to need for certain kind of pages. The linked conversation has the added bonus of explaining how to avoid this.

I mean per-page css/js/html. I will try to explain myself with an example: Supose I have a blog in my site, in which every page has different fonts, perhaps different column, etc, just like in a printed magazine. The blog posts all use the same fields: a title, subtitle, excerpt, body, authors, etc... so it would make sense for all to use the same template. But also, they need custom css/js for each page. As you say, I would like to be able to set this changes from the backend. Bur how would I go about it?

Thanks a lot for your answers. I have a follow up question: is it possible to have art directed pages (pages with custom css, js or html) in processwire? I've yet to find any documentation about this an it is an important feature.

Hi, there, ProcessWire community. I'm seriously considering ProcessWire to make a Magazine-like site. But first, allow me to indulge in some history. Two years ago I was searching for a CMS to make a site for a magazine. I remember Processwire seemed very attractive but in the end I chose Wordpress. Boy did I ended up regretting that decision! Not that the site doesn't work, it works just fine, it just that maintaining it has been such a pain in the ass (and ended up stealing editing time, as I was also the editor). This year, as I transition to a new position, we hired a developer to simplify the admin burden that's currently placed on the very small staff of the magazine. With more than 2,500 posts, all of whom depended on custom plug-ins, we decided that moving out of Wordpress was out of the questions, even if it took so much time, we were to invested in it. In conclusion, I don't wan't to fall into the same mistakes and now I'm thinking about building a new site for a new in ProcessWire. It seems like it can already do a lot of the things my previous site did without the need of plugins: tags, categories, multiple authors, multiple post formats. But some plugins I think I will need, such as the one for adding fields to images (for properly crediting the images). I would also love a Markdown editor, which it seems currently doesn't exist. So I have a few question for you: * How stable are plug ins? Am I going to run into the same problem as Wordpress, when plugins stop working from one update to the next? * How easy is ProcessWire to update? I'm chosing it in part for the roadmap, and I want to take advantage of new functionality when it approaches? * Will 2k visitors, 6K pages daily be any problem with ProcessWire? * Can I have a template for a single page? * How come there's no markdown editor? I am mainly an editor with some self taught front-end skills. All the php I know is from this last two years battling against Wordpress. I already feel I'm a little over my head but I hope I'm making the right choice