Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/17/2014 in all areas

  1. Hi, I just completed my first site design in ProcessWire... http://miraopalinska.com I'm more of a designer than a coder (and had never coded a single line of PHP) so the learning curve was a little bit steep at first, but the patterns started emerging and the consistent way in which Ryan has set up ProcessWire made things a lot easier. I've been using TextPattern extensively, but was starting to find it a little bit clunky for my needs. ProcessWire, without wanting to slam TextPattern, is on a different level. One of the best things? This forum. It seems that absolutely ANYTHING I had a problem with, a search in Google brought me to this forum and an answer. That's a big difference from TextPattern (well, any other CMS to be honest). This forum is a condensed mine of information. So... thank-you everyone here! This was also my first multi-language site, and ProcessWire has that sorted too in a very intuitive, very integrated way. I'm still having a few problems here and there (CKEditor is acting a bit weird, for example), but I'm sure I'll be able to iron them out. Mira's finding it really easy to update and add content. I was able to make the client side really clean and fuss-free. Something that was hard to do in TextPattern (and is a total utter nightmare in WordPress). Installation was pretty basic, using the default admin theme. I used the following modules... CKEditor ImgMinSize Image cropping tool Video embed for YouTube/Vimeo Multi-language Repeater Everything else accomplished with a mix of Javascript and PHP. Thanks again, particularly Ryan. I'm pretty confident I'll be using ProcessWire for all CMS needs from now on. Douglas.
    18 points
  2. Actually I thought it would turn out that those masks indicate the testers of Apeisa's new shopping cart and it is some clever marketing stuff going on... But this whole topic led me to pathetic thinking about the ProcessWire community instead. I think it is great that we, the people of different countries, nations and races can joke around while making something important together instead of oppressing each other with warfare, sanctions slander and such. This type of communication can make real progress in establishing some understanding and mutual respect instead of suspicion and hatred. I am thakthul to this community and it's spirit. Not a master with this kind of language, so pardon my grandiloquence. I usually prefer irony. I havе no television at home, but yesterday was visiting someone who has )).
    9 points
  3. We are all humans Ivan, borders & nations are not build for safety (in first place) instead they are the result of people controlling other people for gaining power. People are competitive by nature. I don't like to use races in this context, cause that is just evolution, adapting to the environment they are living in over a long periode of time. We as human have to question everything, even the things we think we know. Most things are just learnt by confrontation with the subject very often and taken as granted, thus making it 'truth'. We have a fine community here, caring for each other, caring for the things we believe in and believe in the goodness of other people . It's not only the quality of ProcessWire that makes this community thriving the most important part is the social part over here.
    8 points
  4. Apologies for the confusion Ivan, I had no idea that asking my avatar to wear a mask would lead to confusion about the shopping cart module - there is no link between the two. I'll let my avatar know that he nearly caused an international incident in the PW community!
    6 points
  5. Hi all, This theme is now part of the core. You can install it instead of the default. Ryan and I are still working on a few minor issues, but overall it should be really solid. Looking forward to hearing what you all think.
    5 points
  6. Just wanted to throw in my two cents. If you come at it as a front-end developer that's a complete beginner to CMSs, then PW should be very easy to get going. It's built around working the same way that existing web technologies work… Pages map in the same way that URLs do… Template files are just plain HTML/PHP files… the API is largely the same as a front-end API (jQuery)… and so on. So if you know your basic web technologies outside of CMSs, then you won't find a simpler system than ProcessWire. The problem is most other CMSs don't work that way. So the line gets more blurry when you've become used to the terminology and approach of another CMS, because PW can be quite different. Sometimes you have to unlearn what you know from elsewhere in order to appreciate the simplicity of PW. People are always trying to find complexity that isn't there, especially those that grew up on other platforms. PW is a system that rewards you by being curious. We aim to show you how to fish so that you can catch the big fish. We're not here to catch the fish for you. You don't have to know anything about fishing, but you should know how to yell for help if you fall in the water. And you should be willing to learn by example. I learn best by example, so this is the way I tend to teach too (and I recognize not everyone learns the same way). PW is a CMS and CMF, not a website builder. If you are curious and willing to explore, you'll find it is very simple indeed. Certainly far simpler than even WordPress in creating a custom website. You do have to come from the point of view of "I want to create and have the system adapt to me" rather than "I will create something based on what the system provides." If you already know what you want to create and it's something unique, you won't find a simpler path to get there than PW. WordPress is a different beast, in that it's basically saying "YOU WILL CREATE A BLOG or modify this blog and call it something else." Some people like that underlying structure… "okay, we're starting with a blog, what can we do with it?" Others do not like that underlying structure. Our audience consists of those that want to have a system support their original creation rather than mash up an existing creation. There was a PDF posted earlier that I think hit upon some good points, and I appreciate the effort that went into putting it together. The fictional character being scripted in the dialog is not our target. I can go into specifics if anyone wants me to, but I was definitely left feeling at the end of it that we have to be careful about hand-feeding too much or else we'll start attracting people beyond our support resources. Folks that want the fish cooked and filleted rather than folks learning to fish. Perhaps in time we will want to attract more of the consumer-type audience, but currently I don't know how to support users looking to find all the answers in a sitemap file. Keep in mind that unbridled growth is not necessarily desirable. Most of us don't get paid for most of the work we do here and we do best if we grow in a more healthy manner, attracting more thoughtful designer/developers that are here to learn and also contribute. Obviously the author of the PDF is one of the thoughtful ones (and the PDF is a great contribution), even if his fictional character isn't necessarily, but we'll welcome him anyway. But we will definitely be going through the PDF in more detail to learn and improve from it where appropriate, while keeping our audience in mind. I think we're doing something right, because our audience is growing rapidly. I'm nearly full time on ProcessWire now, and it's still difficult to keep up with everyone. At present, I like that our audience is largely open-minded, curious and thoughtful designers and developers. Somehow we've attracted an incredible quality of people and that's what makes this place great. We could not ask for a better group of people here. I'm reluctant to lead PW towards a website builder direction because I think that's when the quality of the community could go down, as people come looking to eat fish rather than learn, catch some fish, and throw some back. The reality is that part of our long term goals include converting the rather large audience that has outgrown WordPress into ProcessWire users. I'm convinced that we do that by giving them more ProcessWire, and not more WordPress. But at the same time, we always have to keep an eye on WordPress and learn. They've been lucky no doubt, but they are also doing many things right. So we have been and always will be working to make the WP-side of users more comfortable in ProcessWire, while also trying to help them grow by distancing them from the limited WP mindset.
    5 points
  7. I would hope someone would have the courtesy to send me a pm, if they really had critical thoughts about my work. I would appreciate and take that better. As I tell people that I mentor, It's all about intent and purpose. Just my two cents.
    4 points
  8. Thanks you both for the great effort keeping with the enormous pace! I just dropped the pack on a 2.5 installation I'm working ATM and looks good so far, will try to report if I find something.
    3 points
  9. I liked the nav too. If you ask a room full of people what they think there will always be a difference of opinion. You don't have to change things people have suggested of course but you may find you get more suggestions here than other places
    3 points
  10. Hi douglas81, As a former TXP user (nearly 5 years) It's always nice to see folks making the transition to ProcessWire. Very nice site. I agree with some of diogo's suggestions about the menu — but in the end it's a pretty small site, so I think people will find their way even if you keep it as-is. You mentioned being more of a designer than coder. I would have described myself the same way when I first started using ProcessWire. I suspect that will change the longer you are here. Anyhow, congrats on the site — and welcome.
    3 points
  11. I just upgraded my processwire, I tried it and love it good job renobird and don´t call me bald please!
    3 points
  12. I installed Craft some days ago and was well impressed with the interface and flexibility, but after playing around a bit and reading their docs I got the idea that it is not nearly as flexible and powerful as PW. I also have the feeling that they managed to have such a clean interface by giving less flexibility, because each field works in a completely different way, while in PW all fields use the same repeatable resources.
    3 points
  13. you need learn how to fish? OR you should learn fishing?
    3 points
  14. Okay, I had to back track to make sure you were not talking about me! I know my luscious long brown (or used to be) hair can be confusing, but......
    3 points
  15. Anyone else tried the new Reno Theme by RenoBird (Tom) ? Looks reall nice and would definitely recommend it. BTW that does say 2.5.1 in the footer
    2 points
  16. Well, you'll need the wireframes for each of your options so I'd suggest you prepare them then contact Ryan to see if its on his roadmap. If not, the ball is still in your court as to how to proceed.
    2 points
  17. Thanks to Manfred's relentless efforts (and a little merging by me), the German language pack for the stable version of ProcessWire is now officially updated for 2.5. I have to admit the merge was a bit of a rocky road, so if anyone notices any issues with this in 2.5 (I have only checked it briefly myself), please report them. The best way to do so is via the language pack's GitHub issues.
    2 points
  18. Don´t worry just kidding. The theme is awesome no issues for me. bald -->
    2 points
  19. Hey Peter, To avoid confusion, you should change the status of Admin > Pages > Image Crop to "hidden" so it doesn't show in the Pages submenu. I have reminded Antti about this (https://github.com/apeisa/Thumbnails/issues/23) so hopefully it will be fixed in Thumbnails shortly. Cheers!
    2 points
  20. blad (bald), Apologies if I ever referred to you incorrectly. I post from mobile a lot, and autocorrect can be a little bastard. Thanks for the kind words. Also, shall I send help? It appears the weight of your mask was too much for your neck. I'm not 100% sure what you mean, but the Pages menu item is one of the things still being sorted out. Pages was just a single parent item when I first built this theme (it's been around over a year now), still exploring other solutions for how that item and it's children work. Keep an eye out for updates.
    2 points
  21. Good job and welcome I love the homepage photo
    2 points
  22. @LostKobrakai Although it might not be the best solution, have you tried something like Textile before? There's a module available for it and you'll need to use the restricted version if the input is coming from untrusted sources like social users. It should handle the differences in \r, \n, \r\n etc but might be a little more complex than you really need. Whatever you end up doing I suggest you always pass the finalised field values through htmlspecialchars() or htmlentities() before rendering them on your site.
    2 points
  23. Better be carefull! A few pixels just started a media virus spreading across the planet.
    2 points
  24. The latest pw 2.5 even has a multi-language installer included with a language selection nav bar.
    2 points
  25. Related to Pete's 3rd point above: It might be helpful to potential respondents if people posting jobs here would also state what timezone they are operating in.
    2 points
  26. @NorbertH If I understand you right, you don't like all those markup-string concatination, which gets stored in variables, like this: foreach(){ $out .= "markup"; } I don't like it as well. At least for more advanced snippets of more than 2 or 3 lines. Your prefered way of php templating does output text directly which isn't great either for a deligated approach. That's why I'm using the TemplateFile class of ProcessWire. It let's you define a html-template in your prefered way, while most of the logic can stay in the processwire-page-template files. // tpl/tmp_article.php <div class="article"> <h2><?php echo $title; ?></h2> <?php echo $text; ?> </div> // articles.php <? $content = ""; foreach($pages->children as $article){ $t = new TemplateFile($config->paths->templates . "tmp/tmp_{$page->template}.php"); $t->set( "title", $article->title ); $t->set( "text", $article->body ); $content .= $t->render(); } As the template files are normal php files as well you can still do what you want to. The $t->render() method just returns everything that gets outputted by the template file.
    2 points
  27. I agree with this. Perhaps a bit wider at 250px? THANK YOU FOR THE POST ABOUT THE AUTOUPDATER I upgraded from 2.4.18 to 2.5.0 without a problem. --- @Ryan THANK YOU!
    2 points
  28. You shouldn't edit index.php directly. Instead you should create a file called index.config.php and put the following there. <?php if(!defined("PROCESSWIRE")) die(); function ProcessWireHostSiteConfig() { return ["*"=>"myNewSiteLocation"]; } Obviously change the string myNewSiteLocation. Edit: Forgot to mention that if your directory name doesn't start with "site-", you should create your own .htaccess inside your site-directory that protects assets in the same way the main .htaccess does. The main .htaccess protects only the default site folder and folders starting with "site-". You could modify the main .htaccess too, but again you should avoid editing it to make upgrading PW easier.
    2 points
  29. I don't understand why you would drop this in relation to this particular thread? Of course there is room for criticism. Nobody made a problem of your point and Peter asked for further input from you, but instead you come up with this slightly off-topic reply. In this case, i and some others don't share your critique. That's the point of having an open discussion. If i would have agreed i would say so as well.
    2 points
  30. Having moved my current Processwire installation to a vanilla LAMP stack, the Responsive Images plugin is finally working! After testing it out and making it work with my picture gallery and maybe even the Lazyload plugin, I will come back with some feedback. I also might consider opening a new thread focussing on the plugin's latest features. Cheers, Stefan
    2 points
  31. Oh yes - Ryans post screams to be put on a subsite like processwire.com/philosophy.
    2 points
  32. Hehe. I must admit that some of my favourite brews right now are actually from the UK. But like my CMS preferences, they're from micro breweries and not the usual, obvious choices
    2 points
  33. The headline is fine - good strong copy and journalistic style. It is called "setting your stall out" and sets the scene for an article. And the gentleman is in the wonderful Dublin; the spelling of the word favourite is fine. Nice to see proper English even after all that Guinness/Murphy's....
    2 points
  34. Install page path history and rename with confidence.
    2 points
  35. Yeah, I appreciate Ryan's feedback, as well as the others. Although I may sound a bit locked in my own vision to some people, it all actually makes me rethink me own expectations about this system, and more important: my current and future situation and livelyhood. So thanks for making me have a small existential crisis, LOL BTW Personally I don't like Wordpress at all, so I don't hope anyone suspects me of being a Wordpress fan, heaven forbid. @Nico: Did your father use the default or the Argos backend?
    2 points
  36. This module may get put into the core. Not sure yet. But it does seem like something that may be useful to most PW installs, so seriously considering it once it's fully refined and has a few miles on it, etc. No need to worry – if you click it, the next screen tells you that it is a downgrade. Though it's perfectly fine to downgrade or upgrade between master and dev, unless using something that's only in dev. I've been doing it all week. This is consistent with how PW currently renders all system notices: at superuser login. If it's an error, it shows up red. Otherwise it shows up green. Upgrades to core or modules in PW aren't particularly important most of the time (since it isn't WordPress). It's more just an "FYI", "if you are looking for it" kind of thing. The info is always available in Setup > Upgrades. But I hear what you are saying and you aren't the first to say they tune out PW's green messages. Antti and I are working on a new notifications system and I expect we're going to do some great things there. This module will be one of a few we use to test the new notifications system. But until then I thought it best to keep consistent with the way PW currently does things with regard to system notices. So just wanted to mention there are some nice new things coming here, but for the overall system rather than just 1 module.
    2 points
  37. Also wanted to add this as a disclaimer for this forum: Any arrangement for work made via this board is a private contract between the individuals concerned. ProcessWire and Ryan Cramer / Ryan Cramer Design, LLC or any of its agents cannot be held responsible for the operation of that contract or any of the financial arrangements and will not get involved in any disputes under any circumstances. If it goes wrong for any reason, it should be sorted away from this community. Thanks to Joss for the suggestion and wording.
    2 points
  38. Is my 100th post I wanted to do something special. I edited a video, hope you like it Just for fun Edited: Now with subtitles
    1 point
  39. You are overwriting the $pictures variable in each loop iteration. It will only ever have the last image in it that way. You should concatenate instead. Something like this... if(count($page->images)) { $pictures = ''; // if the page has images on it, loop through them... foreach($page->images as $image) { $image = $image->width(400); $pictures .= "<img src='$image->url' alt='$image->description' />" . "<blockquote>$image->description</blockquote>"; } // output the images at the top of the sidebar $sidebar = $pictures . $page->sidebar; } Note that it is now $pictures .= "..." rather than $pictures = "..."
    1 point
  40. Sorry for bumping in here but coming from Joomla/Seblod I'm still very green when it comes to php and processwire. I love this new world though and I'm setting a responsive site for a local soccerclub! I went through the docs and Kodongo's tutorial yet there is a snippet I can't find so that for each teampage I can call a unique 'team'category of the blog: So I first put: $blogOut = $modules->get("MarkupBlog"); Then things like $limit = $page->blog_quantity; $content = ''; //$content .= "<h2>$page->title</h2>"; //Render limited number of posts on Blog Home Page $content .= $blogOut->renderPosts("limit={$limit}"); ?> <div id="main" class="block"><?php echo $content?></div> But what/where do I put the fact that I want that output to be filtered to only render the output of ONE category (for example) 'Fanions'? I'd really appreciate your answer as it will open my eyes to much more! Bernard (ps. The site I'm creating is kcfheist.be and one of the teampages where I want to put the blog as tab n°1 sits HERE . Note that for all the teampages the trainers and players(spelers) are filtered by a 'select multiple fieldset' so that next year they will appear in both this years team and the team they will belong to next year. Same for the sponsors which all are children of the same parent. Should they want to sponsor an additional team, Then I olly have to tick them 'on' in order for them to appear in another Teampage too)
    1 point
  41. @renobird Thanks! Yeah, I was in touch with you a few months ago when I was thinking of making the switch from TXP, and now here I am! I hope I don't become "more of a coder than a designer", but I'll be happy if the balance evens out a bit. I saw (for the three second I had PW2.5 installed) that you have an admin theme included as default. Look forward to seeing how that looks as it was your blog post on a new TXP admin which brought me over here in the first place.
    1 point
  42. is this alpha, beta or released? @ivan https://github.com/Renobird/AdminThemeReno
    1 point
  43. Back to topic : A lovely site! Me myself I'm a former Textpattern user and will always be thankful to it, because Textpattern introduced me to the freedom writing you own markup gives you. If you stay with PW you'll meet other fellow Texpattern users here.
    1 point
  44. I'm new to ProcessWire and I have some immediate editing needs that I can't figure out how to do. I like to hire some professional help to make these edits and also teach me how to make them. I really need help ASAP! Please contact me if you can help me out and your hourly rate! I suspect I need 2-6 hours of help and I will pay quickly. dan@gravityim.com Thanks, Dan
    1 point
  45. Cheers 3fingers. They're on my tiny things list IE the massive list of tiny things I need to find time to do I think it's the Foundation framework which is auto-generating these ugly things. The select lists are not in the actual templates.
    1 point
  46. I'm giving out an implementation which you can use while Ryan is considering this matter. It's based on Ryan's FieldtypeFloat and InputfieldFloat and it should cover all the basics. cd <pw_modules_directory> git clone https://github.com/sforsman/FieldtypeDecimal.git git clone https://github.com/sforsman/InputfieldDecimal.git To actually use them, you obviously need to tell PW to scan for new modules and then install them. Couple of notes Since the precision needs to be defined on the database-level, this module hooks ProcessField::fieldSaved and updates the database if you have changed the precision settings. You get a notification if it's been done. Be aware, if you decrease the precision you will obviously loose those decimals forever after the save - the database is immediteally and always modified. I don't consider this ugly because this is mandatory - one way or another. Due to the implementation of the DECIMAL type in MySQL, it's not possible to choose such default values that would be optimal for all of the different scenarios. Along with a dot, I prefer to accept decimals with a comma as well. This is because many humans separate them with a comma. As with InputfieldFloat, you can define the range of the values the InputfieldDecimal will accept. If you have a precision math library installed, the module will use it when doing the comparison. This will rarely make a difference but hey, what the heck. To be consistent as to how the DECIMAL type is created in MySQL, the digits-parameter refers to the the total number of digits - including the decimal parts (5.55 has three digits and two decimals). There's a few known "issues" (I prefer to call them "features", though)The min/max configuration Inputfields are still using InputfieldFloat. This means you need to separate decimals in your min/max range with a dot. The sanitizer currently uses is_numeric() to check the value, which means you can enter some weird stuff (like 0x539) and it's sent to the database. However MySQL obviously ignores such values and stores 0 for you. This should be improved later. The Fieldtype doesn't do much to the values and relies on MySQL to handle the necessary rounding etc. This is good in my opinion. However this also means that if you have set the precision to "2" and enter a value that doesn't have any decimals (e.g. "5"), MySQL will add the decimals (the DECIMAL type is afterall an exact fixed-point type) and that's what you will see after you have saved your value (e.g. "5.00") . Again, I consider this a good thing. Like InputfieldFloat, the InputfieldDecimal doesn't do any validation on the data - invalid values are just blanked. As I have intentionally hooked only ProcessField::fieldSaved, you need to manually either a) call $field->type->syncSchema() or b) hook Fields::save yourself if you are modifying the precision of a field through the API. Oh and I'm open to any ideas - at least regarding these modules.
    1 point
  47. Launched http://www.greggorrauto.com last week! Responsive Theme built with Bootstrap 3 and Processwire! Uses the bootstrap carousel for the slider, and the Affix.js to keep the right column on the inventory search page sticky on scroll. (If the screen is tall enough.) Also uses a modal style lightbox on the inventory detail page as well as animated scrolling to anchors. I know I used the Google maps marker module and the form templates processor module. Also using redirects and batcher. (Redirects for the sub menu items for the price ranges. It just sends the user to the search page with the correct query strings. The homepage slider is managed with the image field so I can drag and drop new slides up, but I didn't know how to manage both the caption and the link url using just the description field, and I did not know how to add another one, so I did a pipe delimited. ie. image caption|http://www.linkurl.com format is used in the image description field. If its easy to add a second box to separate those out, let me know! Also, let me know what you think!
    1 point
  48. Manfred, just wanted to say a huge THANK YOU for your effort! Very appreciated!
    1 point
  49. After writing it all up for that forum post, I wasn't satisfied with having to make edits to two templates in order to enable the feature. So I've gone back and re-done this feature. The instructions and screenshot have been updated (see my post above). Now you only have to edit one template, and all settings related to it are in the 'Family' tab. I've also added a "title" option, where it will auto-generate your page name from the title, just like you are probably used to. Because the title isn't yet known when the page is created, it assigns a temporary name to the page, then overwrites it once you give your page a title.
    1 point
×
×
  • Create New...