Jump to content

diogo

Moderators
  • Posts

    4,287
  • Joined

  • Last visited

  • Days Won

    79

Everything posted by diogo

  1. Great news Ryan! So I still recommend structuring your site with multiple trees rather than relying on multi language fields I still think these fields could be useful for this. Couldn't we have a way of calling the field on the language we want like this $page->title->es? Like this we could still prepare one page for each language, and have a friendly form for the editor.
  2. I'm glad Ryan came to help. Rob, I still think I wasn't that far though, since repeatable fields will make all this process so much easier.
  3. Welcome to the forums Tall (for abbreviation) Repeatable fields are on the roadmap only for August http://processwire.com/about/roadmap/ The subject is being discussed here http://processwire.com/talk/index.php/topic,53.0.html, maybe you can also throw some ideas. UPDATE: I would bet that there will be a module even before August
  4. Ok, I will use inline for now. thanks a lot for the answers!
  5. In this case it's for a simple construction page. There will be three circles with some info and i want them to be in different positions every time the page loads.I only need dynamic margin-top and margin-left for each circle. For this one It's only one page, so I think I will do it as Apeisa suggested, but I was also wondering how to do it on a bigger website, even if it's only to have variables on css without using something like Sass.
  6. Thanks for the suggestion. Fixed that as well. Nice, I think it looks more integrated like this
  7. What would be the best way of having dynamic CSS in all pages without making it heavy to process? external style.php with a content-type header instead of style.css internal stylesheet on header.inc, or on a dedicated include other
  8. Ryan, here are some links about the symphony module. It's called "Subsection Manager". There's also a vídeo. http://symphony-cms.com/download/extensions/view/41121/ http://symphony-cms.com/discuss/thread/41122/ https://github.com/nilshoerrmann/subsectionmanager/wiki/Subsection-Manager http://vimeo.com/22333100 UPDATE: oh, and a more recent one http://symphony-cms.com/discuss/thread/50421/
  9. Much better I would also change the color of the links to be the same as the titles. They would still look like links, but with a less default feeling. I's a tiny change, but I think it makes a difference.
  10. That was quick This solution solves the problem well, thanks!
  11. Pete, thanks for this module. I'm using it in two under construction webpages. However i have one concern. Because it redirects to one page, the URL changes, and i'm worried that visitors might bookmark it instead of the real page. If so, when they come back, they might think the website is still under maintenance. Is thee any possibility that the change wouldn't reflect on the URL?
  12. Speaking of symphony forums, i have the feeling that this will be very interesting http://symphony-cms.com/discuss/thread/79645/
  13. For me they are also both very slow. Your personal website is pretty quick though. Nice post about pw
  14. pretty quick reply here, because i'm in the middle of something. I had the same idea in January (last paragraph) Ya, It's quite true! It's a pitty that it was so unnoticed by then. But it doesn't even have to be done with ajax, processwire API can take care of this by its own, no? I think that in symphony cms there is good implementation if this method. http://symphony-cms.com/download/extensions/view/41121/ You are referring to this right? I remember it from when i used Symphony on one project. As i remember it's a slightly different approach and the implementation didn't feel that natural. Maybe because of the way Symphony works. I think in Processwire it would be much simpler to do it. Anyway, as i told in other threads, Symphony it's a very well thought CMS, and it touches PW in some points.
  15. Nice! I'm glad you liked the idea It occurred to me that it might be less simple to do it as i imagined. If inside pages there are already children, The children created by the field would be mixed with them... quite confusing... Instead, maybe it would be better to have a special page dedicated to this field type (like the admin page, or the trash page). > Admin > Repeatable field type > Edited page A > Repeated field of A 1 > Repeated field of A 2 > Repeated field of A 3 > Edited page B > Repeated field of B 1 > Repeated field of B 2 > Repeated field of B 3 > Trash
  16. The CMS is much better than it's reputation. You will see for yourself
  17. For answering to this http://processwire.com/talk/index.php/topic,621.0.html, i revisited this thread and thought again about it. Maybe this can be done without breaking the way processwire naturaly behaves. This field type could simply mirror inside the edit page one branch of the tree. It can be only an interface to create children of a page from inside the editing of another page (or even the same, whatever...) So, while creating the field, we would only have to define a preexisting page to be the parent of our repeatable elements. On the edit page, this field type could work much like the image field already works. When adding a new repeatable element, a new page would be automatically created under the parent that we defined while creating the field. The fields for each element would be the same from the template that was chosen for the children of our parent page (or could be even different for each element of the group if the editor as permission to choose the template). Templating would target the tree normaly and ignore this field.. The editor would have the feeling of creating repeatable elements inside a page, but everything would still work on a processwire way. Would this be easy to implement has a module? I'm getting quite sleepy but i hope i was clear enough
  18. This was discussed before. Here is the topic that lead to the inclusion of repeatable fields on the roadmap http://processwire.com/talk/index.php/topic,53.msg168.html#msg168 Like Soma said, the default way of doing this in processwire is using the tree
  19. Nico, is this what you are looking for? http://processwire.com/talk/index.php/topic,598.0.html maybe you can also help
  20. Hi Neildaemond, welcome to the forum. I never had any issue like this while installing processwire, and i couldn't reproduce it with any combination of permissions. But what you are describing sounds very similar to this http://processwire.com/talk/index.php/topic,597.0.html Hope it helps
  21. I think the forum is positive like this, having good comments about a bad comment. If Soma deletes the comment, then all the other comments don't make any sense and also have to be deleted... It will mess all the thread. I don't see any harm on keeping it like it is.
  22. I imagine that Processwire potential users also look for markup freedom
  23. yaaaaaaaaaaaaaay!!! PW will get the deserved attention now
×
×
  • Create New...