Zahari M.

Hi guys! Having installed fellow member Martijns delegate profile and seeing how he used Fieldsets, I went about creating field sets of my own and then adding them to my template. All was good!! BUT... I then tried cloning a field set. It cloned it just fine. But ever since cloning that fielset... I cant add ANY fieldsets to the template. They are no longer listed in the Add Field dropdown... Any ideas on things I could try to recover from this situation? Im not at all familiar with the database schema but would be happy to go in there to change any values to see if I can get it all working again. Anyone have any ideas on what I could try? Cheers guys! ================================= Edited and sorry, i could not delete this post ================================= OK.... Its Fixed and Im a dummy indeed!! What happened is that as my list of fields grew, when I hit the add field button, I did not observe that there was scrollbar and that the list of items in the dropdown had grown to the point that new additions were no longer visible. DUH!!!! Apologies

Hi Martijn Your diagnosis was spot on! It was due to me changing the admin url. You know PW very well! I reinstalled everything and edited view.inc as before and now the edit button on the front end works. Yay! By the way.... I tried to look for MarkupCSScompress in sites/modules but it is not included... or at least I can't find it! So I went to the ProcessWire modules page to look for it and download it. I'll try it out later on once Ive worked on those sidebars. Anyways... Thanks again Martijn! Cheers

Thanks Martijn and Soma for your replies! 3 great approaches from you both. That's awesome. I never thought of moving out a core module to our sites folder and modifying it. But I feel most comfortable with that approach and I'm happy going with that. Thanks for that link Soma. It contains a very instructional concept of great value. Nontheless.... I still think it would be of great value for the comment form API to be able to accept a class for the submit button without using any of our workarounds! We can currently configure just about everything else that is needed via the API, so why not the submit class as well? I'm very certain more people in the future who want to style the button would be looking for it expecting to find it in the API Anyway... it was just a wish Cheers guys!

Hi Martijn That fixed it! Thanks for that. Just as a note... on the front end... if we press the edit button in the top right corner, we get a 404 for the main content. But Im thrilled that I downloaded this site profile. I learnt two things from you Martijn. One is that the way you split the admin area 60 / 40 and used fieldsets. Very nice. The other is how you used that range slider. Thats fabulous! I'm very glad I downloaded this. Thanks for all the work here Martijn! Now... to go look at the widgets...

Hi Martijn Thanks for your reply earlier. The site you pointed me to looks really nice. And that gumby framework looks outstanding... very nice looking indeed! Ok.... so I have tried to install that delegate profile in MAMP but I have come across an error that is preventing the front end from displaying... admin side is fine... just the front end has a white screen... Error: Call to a member function render() on a non-object (line 44 of /Applications/MAMP/htdocs/delegate.dev/site/templates/includes/view.inc) Looking at line 44, we have this: <?=$modules->get('MarkupCSScompress')->render()?> Any ideas what we need to do to fix this Martijn? Thanks!

Hi! Thanks for the reply mate! I'm on mobile now so I will take a look at the links you posted later.... Sure am glad I asked!!

Hi Guys Slowly getting into ProcessWire Bit by bit the sites coming together. So, Im going for a 3 column layout. I'm just wondering what strategies you guys are using to display your sidebars. I'd like to create conditional sidebars depending on what section of the site the visitors are in and am just wondering if any of you have done this and how you went about it.... Since Im using 2 sidebars, I was thinking of using 2 parent pages and various child pages to represent each desired sidebar. But before going further with this... just wondered if anyone has gone down this road before! Cheers n thanks for reading...

Hi Ryan Been working on styling the comments form and have come across the need to add classes to the submit button. This is to add two Zurb button classes... small and radius. To do this I had to go into the core to modify CommentForm.php As others in the future may wish to style their submit buttons, it would be great if you could add the option for button classes when we run this... echo $page->comments->render(array Thanks Ryan!

Thanks for this diogo ! After reading how many here seem to like Sublime, I downloaded ST3 and I have to say it was very interesting. After installing the package manager and downloading the Soda theme and configuring it, it was great. After downloading a color scheme for Soda and just tweaking the color for comments, it is now awesome!!! I look forward to the SFTP package (commercial) for ST3 to be released so that it can send files to the server. I also like that the sidebar can easily be hidden with a keyboard shortcut and that when it is visible, thanks to the soda theme, it looks rather Mac OS X like... So thanks to all the ST guys here for suggesting this... Cheers guys!

Hey teppo Many thanks for that! That's a good link you put there! I guess I shall stick to www this time round... But I will also add your code into the htaccess comments file for future needs Teppo... Thanks mate!

Hi Guys! Not very good with htaccess files hence the question... The standard PW .htaccess file gives us the option to redirect non www to www... # ----------------------------------------------------------------------------------------------- # Optional: Redirect users to the 'www.' version of the site (uncomment to enable). # For example: http://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301] How would we do the opposite? Cheers guys!

Thanks for that link kongondo! I was thinking a bit about this after reading that link..... If i had a blog and each post had a featured image, then the "practical limit" for the maximum number of posts would be ~ 30,000 posts due to file system limits. Be interesting to see how this one gets overcome eventually. Fortunately for me, Im not a prolific blogger

For everyone who has replied, I am very grateful to you. But this will be the last time I will be checking into this particular thread as I obviously cant articulate the problem clearly enough. And the truth is I'm getting a lil bit fatigued with some of the responses that instead of looking at what might be missing, rather champion the current "status quo" of things and how someone is expected to learn!! Lol! Kinda ironic and funny But no worries. No offence at all is taken and again, I have so much to learn from you guys and am very grateful to all of ya! Thanks kongondo for offering me the facility to ask you some questions. I appreciate that and certainly will be doing so. I've got the first couple of videos kinda worked out. They will be on how to enter content in. It's the getting it out, or rather getting some of it out that I'll need your help with mate! Cheers guys

Thanks for sharing the solution here Allan. Works for me too! Cheers

Hi kongondo I think you and I agree on a lot of things and would be good mates at a pub! This threads exchanges have only further illuminated to me that I have a very different philosophy on how ProcessWire can best be learnt when your approaching it as a beginner. I disagree with a few things that have been said here. But Im not one to want to argue. The fact remains that someone like me finds it difficult to learn ProcessWire for the reasons I outlined. No matter. I will go ahead and do things my own way and make my own tutorials with snippets . Perhaps they will only make sense to me and a few others as it appears that Im in a minority in all of this. But thats cool Anyways, cheers guys! Still lots to learn from all of ya!

Interesting.... you two guys are the nicest and most helpful here!! But from what I see in your replies, both of you "seem" to almost think that the "current" state of documentation is "good enough". Some here also seem almost to champion the point of view that PW doesn't assume things and hence doesn't include many things. Well, Im here saying that these points of views are creating a real barrier of to entry to ProcessWire for "some of us". They are almost elitist responses. Im totally with the concept of not including anything as standard. But anyone who would be coming here from WordPress would want a tagging system. Why? Because such functionality transcends any CMS. They would want a tagging system because it offers such great value to everyone. It's got nothing to do with WordPress. What would be great is if there was a self contained "tag recipe" that worked through how one could build a tagging system. Maybe such an article exists already? i dont know, because I would have to go and hunt thru all the threads to find it to know this. It's just not obvious to me where to find it. Yes, yes, there is a blog profile. But for a newbie, you are having to grasp with such an incredible amount of information all at once that it is overwhelming. I would like to reitterate my point. Its' not that there is anything wrong with the current documentation. It is that it does not have alongside it some good "prefaces" that would help one understand all the docs much better if they read the prefaces. Anyways, what I would ask is this. If there is anyone here who can relate to my situation and knows PW well enough and could help me with some code snippets, please send me a private message. Basically I would want to ask them how to do certain things, and then I can do a video of how to do it. For example.... what snippet would I need to generate 3 random posts. That sorta stuff... Time for less talk and to go make some videos Cheers guys!

Hi teppo! I can't speak for others, but for me, here is what I would say were the "pain points" that I encountered... Major issue is dealing with the "Tree - Pages - No Categories" model for the first time && ( $victim == "comes from wp" || $victim == "comes from d*" ) This took me quite a while to come to grips with. After say a month now, I have come to terms with it all and it is no longer the hurdle that it once was. But when first encountering it, the absence of categories makes it seem so damn inflexible and your thinking how and where the hell do I put my content!!! Only after reading lots of threads on how to categorize content, and reading lots of threads how to "list child pages" does the tree model all begin to make sense. So, what's missing, in my opinion is an "orientation guide" that helps you with some examples of how to lay your content out using a solid parents and children structure, ALONG with a good explanation of how to display our content and any related content alongside it. The problem here is that as there are no "categories" to begin with, ( yes, I now know you can "create" this functionality), your there wondering, if I have 100 articles, how are people going to find them? There are no categories and it would be ridiculous to have 100 artlces linked in the menu. So then you start looking at the code that is thrown in with the templates that generate a list of child pages out of neccesity. But here again lies another problem. ProcessWire too readily assumes you have a very good understanding of arrays and for foreach loops. It's just thrown at you in the starter template and for those who dont have a good understanding of arrays, you're left struggling here. To me, there is a missing guide that says, hey, there's this thing called the page array and here's whats inside it and here are a few code examples to help you access it and that using these code examples will help you list out some common requirements. For example... If your on a parent page and what to list every child of this parent, use this block of code. Now, if there are too many results, here's how you limit them by modifying that block of code here. If you want to paginate, heres how you further modify the code. Once sufficent simple examples have been built up upon, then, I believe, all the existing documentation will make MUCH more sense to beginners / newbies like me, because we have seen a set of code snippets that have "evolved" inside these examples and as such we can now readily recognize certain patterns. Once we are familiar with these patterns, then it's just going into the docs and grabbing just the bit you need cos by then, you KNOW exactly where you are going to slot it in But teppi, these are not complaints on my part. I for one hate these basthirds on YouTube who so readily criticise videos and content when they have no idea of the effort that has gone into it, nor have they produced anything themselves! My response to all this is that I want to make a couple of videos to contribute to the community here to help build a better bridge for some of those newbies who are journeying in towards ProcessWire land and are facing the same difficulties that I am. So, the first video I want to make is about explaining a bit about the ProcessWire templating system..... The second video I want to make is about how to generate a list of child pages.... Coming soon! Cheers teppo!

Not heard of that one. Is it a comedy? Or perhaps a horror movie?

Hi Guys Ya know, I find it illuminating to read here that many of you find PW easy to learn and WP a painful experience. I'm wondering if this might be a left brain right brain thing? My personal experience is actually the reverse! Why I say this is that I find WP very understandable and manageable. In turn I find PW hard to learn. I mention this not to disagree with you guys at all. Just relating that I have found it hard to get to grips with PW. A lot of this difficulty that "I" face is due to the fact that a lot of the documentation that exists makes sense to someone with a certain "development and learning history". So what I am thinking is, depending on your learning history, and the software you have used in the past, much of the documentation for PW makes crystal clear sense, as witnessed by all the exchanges all you guys have in the forums. I see a few "missing blocks" in the documentation that if they were to exist, WOULD make it very easy to learn PW. Our member Joss, I believe, saw these same ommisions, and has created some posts that really helped me "comprehend the ProcessWire way"... http://wiki.processwire.com/index.php/Basic_Website_Tutorial This one really helped... So thank you Joss! But I don't think WP is as bad as it seems to be made out to be here. One of the WP lead developers, Mark Jaquith, uses the tag line, WordPress puts food on my table. From what I see here, it's putting food on some tables here too. And based on what the stats are suggesting, one in every 4 clients may have a WP site. WP skills are a great thing to have. Anyways, Im so glad I found ProcessWire. I think its's awesome and I wouldn't go back. I hope my post doesnt seem like its disagreeing or is in anyway an argument guys!! Just sharing some inner thoughts.... I'm just the newbie student here and am learning a heck of a lot from all of you! Cheers guys

Hi Guys Looking into the site/assets/files folder, there is a folder there for perhaps every single post. Coming from WordPress and Drupal, they tend to group such assets into sub folders, say by way of month/year folders... Of course the ProcessWire way has a simplicity and directness to it. But it looks like it can get pretty big! My questions are.... if we have say 10,000 posts, 1. In the case of Mac users here, does our Macs finder have any difficulty displaying 10,000 folders at once? 2. For those of you who have been there , any tips or suggestions to be mindful off when working with a large number of folders? Cheers guys!

Hi guys I've switched over from WordPress. Perhaps it's better to say that I have graduated from WordPress. I would like to add though that having spent a bit of time with Joomla, Drupal and WordPress, there was much to be learnt from the software and their respective communities in terms of their outlook and priorities. By spending time in the WordPress world for instance, I have come to learn a lot on the subjects of Typography and Search Engine Optimization. Drupal gave me an appreciation for the usefulness for Taxonomy and certain concepts of logic. I thought their token system was a great idea. Joomla, well, it was illuminating to see the long term effects of their project leadership circa 1.5 and what happens when there isn't a clear or prompt roadmap for some of us users Diversity in our world is a wonderful thing. May they all continue to "live long and prosper". I wouldn't be both in instant awe and totally content with my wife PW had I not lived with those 3 bitches J, D & WP ... The rascal that I was... sometimes I would have all 3 of em in the house at the same time...

Hi Ryan Thanks for the bit about type hinting! I didn't know that existed. It now is slowly making more sense. Cheers

Hi diogo! Not enough pages yet to test pagination! Will have to get back to you soon...

Hi diogo Interestingly I was just thinking that the first one might be preferable too! Thanks for the reply! If I could ask you diogo, how could we add pagination into this? Cheers diogo!

Hi diogo Thanks so much for taking a look at this OK... This bit helped... function renderNav($items, $options) { So the pattern now looks a little bit more familiar! So I have rewritten my function to look like this: function renderBlogPosts($items) { if(!count($items)) return ''; $out = "<ul>"; foreach($items as $item) { $out .= "<li><a href='$item->url'>$icon$item->title</a></li> "; $out .= "<p class='summary'>$item->summary</p>"; } $out .= "</ul>"; return $out; } And of course, just like before, it is called like this in the template file: $body .= renderBlogPosts($page->children); So, looking at the original renderNav function and your additional comment or note of writing out $items = $page->children as inspiration, another way to possibly make it "cleaner" would be to further hard code the function. So... we call the function like so: $body .= renderBlogPosts(); And our function has your "line" put into it: function renderBlogPosts() { $page = wire('page'); $items = $page->children if(!count($items)) return ''; $out = "<ul>"; foreach($items as $item) { $out .= "<li><a href='$item->url'>$icon$item->title</a></li> "; $out .= "<p class='summary'>$item->summary</p>"; } $out .= "</ul>"; return $out; } So diogo, both of these approaches work. So thanks for helping me out here with your comments. They really helped. In your opinion diogo, out of the two approaches I have shown above, would you recommend one over the other? As I am a real newbie, I am just not able to tell if any php related code is of good quality. Thanks! Hi kongondo Thanks so much for reading this and your comments. Im with you about studying the blog and skyscraper profiles mate! I actually have them installed already in MAMP waiting to dig into them when time permits. I suppose Im stuck, and very happily so into the Foundation profile at the moment as I was actually trying to integrate Foundation myself a couple of weeks before Ryan released it. But I had no idea how to integrate the Foundation menu and so I find that this particular profile is very helpful to me learning ProcessWire as it has so many solutions to the very things I hadn't a clue how to do!! In the short time I have come to start learning and using PW, what i can see is that one of the core needs I have is to be able to generate a listing of pages for each section / parent page and that is why the creation of a good solid simple function to do just this is important to me. And one that I can understand well. Armed with such a simple solid function, then we can copy it, rename it and edit it slightly by way of adding say an icon to each list item without having to scratch ones head by adding instances of our new additions into the existing array The link you provided me was awesome. Thanks for that kongondo! Your timing for that link was great too kongondo! Having seen how flexible and awesome PW is, one thing that seemed somewhat odd to me is that I cant see a readily visible way in the admin of being able to select a different php theme template file to attach to our "admin template files". These seem to be tied 1:1. From what I gather, if you want to offer different "html arrangements" such as being able to choose to render your pages fields on a 1 column page or a 3 column page, you have to create a new field and add conditional switching in your theme files. I havent looked deeply into this. Just saying it was one strange thing to me. That thread you pointed me to looks like it's just the ticket! Thanks so much guys! Cheers