Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by slkwrm

  1. Thank you @elabx! Corrected the original comment. It's meant for you, @Inxentas.
  2. Hi @Inxentas With ProcessWire, you can use whatever you want on the frontend: Vanilla JS, jQuery, Vue. I would recommend that you take a look at htmx, which seems very interesting and should align well with ProcessWire's philosophy. As far as I know, Alpine.js is often used in conjunction with HTMX for frontend scripting. By the way, there are some excellent essays on htmx's website. I highly recommend reading them for everyone involved in web development.
  3. I see you found your solution, but I will post mine anyway, maybe it will be of some help too <?php $today = strtotime('today midnight'); //or if you want to show only events in future //$today = date(); $schedule = $page->schedule->find("schedule_date>$today"); //then put $schedule in your loop Also you can request one item like this: <?php $schedule_item = $pages->get(1007)->schedule->get("schedule_date>=$today"); //maybe you'll want to sort them if they are not in the right order, then add sort=schedule_date to your selector
  4. I terms of development and usage standpoint ProcessWire is much better suited for the task then Joomla, Wordpress and even Drupal. But you have to be ready to invest your time in learning some concepts of PW. There are a few of them: page, pageArray, selector, template, template file, field, and module. If you feell comfortable with OOP PHP, CSS and HTML, you will definetely succeed. Of course it will requre some custom coding as with any more or less complex project. I'll try to make some assessment here in terms of efforts required if you have the skills mentioned above: listing and search of properties for rent and sale - easy blog layout display and detail display - very easy gallery for each property - very easy google maps display of location - easy with existing module (some work is required if you need more complex integration) google maps search - (not quite sure what you mean here) I guess it depends on what parameters you want to search, should require some coding user registration - user access control is coming out of-the-box, you just need to customise it for your needs and make registration and login forms for your front end. add to favorites function- easy send to friend - easy social share - some coding requred - I think there are open source social sharing projects you could integrate for this (like this one) and so on - it depends, but I think the rest is super-easy front and back end editing - back-end editing is already here. But front-end editing is what you will have to code yourself. So I suppose could require fair amount of work. restricted access to some sensitive informations (like landlords contact details, clients info and so on) - it depends on the logic of your site, I guess you will have to code some parts. adding property informations with some already defined values in dynamic fields (street names for instance) - from easy to medium, but more info would help. Jquery image upload (automatic resize, thumbnail creation, watermark add) - all is here (thanks @Apeisa and @smd) including watermarks (thanks to @Horst) I am sure you get the picture. Unless you have a strict deadline go with Processwire - it will worth the effort in any possible sense. If it's your first project with PW, it may be not the easiest journey, but an exciting one. In the end you will aquire some great skills and have many insights. And I'm sure, after you've arrived you will never look back . Whereas you arguably could start faster with Drupal (that I think the only competitive CMS option here) dropping some plugins together, you then would almost inevitable struggle with your front-end markup and in general making all work the way you (and not Drupal) want. And again you have to be familiar with Drupal's internals to make those hacks. In PW you develope naturally extending existing functionality and it doesn't make any assumptions about your workflow and markup. So it gives you more rewarding experience during the development process. Almost all the skills you get using PW is transferable to other webdev areas. From the UX point of view PW's interface is a dream coming true (and Drupal is a nightmare IMHO). If you haven't seen PW 2.4 yet, just go and have a look - it's beautiful!
  5. slkwrm

    Hanna Code

    @jean-luk Yes repeaters are in fact internal pages, so doing the following should help (not tested): if ($page instanceof RepeaterPage) { $id = $page->parent->id; } else { $id = $page->id; } echo $id;
  6. Ryan, thank you so much for your titanic efforts in pushing PW forward and making it a true top-notch CMS. I'm afraid, my evening leisure time is now, how they say on Bloomberg, "officially compromised". Congratulations, everybody!
  7. This is pretty sweet Great stuff, Ryan!
  8. @Sanyaissues You have to loop through the lines of your csv and for each line check whether the page for your current product has already been created. If so, just add a new brand item to its repeater and save it. If the page hasn't been created yet, add the page, populate its fields and first brand item and save it. That's it.
  9. I've sent this complaint to the organizers: and received this reply: I wasn't able to find @metis community at G+ and FB, only personal pages, their Twitter following 5 times smaller then ours, so this kind of reply makes me really sad. What do you think, guys?
  10. Guys, I've just twitted ‏@SLKWRM asking for help, please re-tweet to support. I hope we still have chances.
  11. Hi, scutter. From the first glance it seems your selector should work as expected, not sure why it doesn't. Have you tried to use $users->find("limit=50") instead of $pages? Does it make any difference?
  12. Hey, k07n. Great website! Looks clean and informative. I must say I love Massive Attack, been twice on their live gig in SPb. My all time favourite is their classic Mezzonine - dark, hazy and trippy album. Pure delight! (Those who watched "House MD" might hear "Teardrop" in its opening titles) For lazy folks I'll leave the link to the album here. Give it a try.: https://www.youtube.com/watch?v=WCwfUX58IZw
  13. Merry Christmas everybody! Sorry for not being here guys, I had to quit web-development for a while. Still come here regularly and read a lot of cool stuff you post. Hey, Valan. I guess this is what you need: Also check out these modules for more granular access control: http://modules.processwire.com/modules/page-edit-per-user/ http://modules.processwire.com/modules/page-edit-per-role/ It should be enough to solve this problem.
  14. RequreJS looks good, no doubt. But does PW really need it at the moment? Will modular loading open new possibilities for backend development? I haven't encounter complains here about issues with using scripts when loading them traditionally. Please, correct me if I'm wrong. Yes, potentially there can be a lot of developers but even then even then, I'm sure, BEM is overkill for PW's backend. Yandex use set of tools to automate BEM project's deploying (can be found here http://bem.info/tools/bem/). Or do you mean using this methodology as guidelines and just hand-crafting css the BEM way? If anyone's interested there's a good article about BEM to wrap one's head around this concept (and don't forget the comments section as there's an interesting discussion going on there): http://coding.smashingmagazine.com/2012/04/16/a-new-front-end-methodology-bem/ this one is also good: http://bem.info/articles/yandex-frontend-dev/ and this can help to understand the evolution of the method: http://bem.info/method/history/ Please note, Yandex has more than 150 frontend-developers and they create super-complex projects that are sometimes interconnected and so the context where the "block" can potentially be used is often unknown so this methodology suits their projects well. I think that more concise "backend's frontend" development guidelines would be more suitable. Or maybe limit BEM's usage to certain rules of its simplified version. IMO the real reason of the backend "outdated" feel at the moment is primarily jQueryUI, which I guess was chosen by Ryan as it provides quick and dirty way to have a very decent UI though not extremely sexy. Sex appeal is a good thing if there's a substance behind it or you are risking to end up with one night stand) Also wanted to mention that to me it's not totally fair to compare PW to Craft and Anchor as they are blogging platforms that have more rigid structure and definite purpose so they can afford to have beautiful interface without thinking about flexibility and adaptability. Craft looks good and can be a role model for PW but what's interesting it doesn't use any progressive frontend paradigms. It seems they have their own homegrown "Garnish UI toolkit" and parts of jQuery UI. Don't know much about this CMS so can't really say anything about its flexibility compared to PW. The best is the enemy of the good. Just a Russian saying) I have a parallel with PHP here: it seems like everybody hate it, but at the same time it's the most used web-development language out there. It works just everywhere and it's possible to start making sh*tty websites in minutes! But then there's a depth and space to grow. So what changes would be required to PW core to make it work the proper way? Can it be injected as an option via PW module? As far as I understand, jQuery is AMD compatible but not all its plug-ins so then one have to shim them. Is it correct? Oh, sorry. I see what you mean now. Does it have to be a js-testing framework of some kind? Yeah, agree. Alternative totlal rewrite of backend is too much. It can be reasonable only if there's a plan to migrate to such new backend in future. I think your idea about a new theme is great. It would definitely help understand what is needed for a better backend. Thank you for your thorough answers and interesting ideas!
  15. Hi Felix, hi everybody. Long time no see! I have mixed feelings about this idea of pimpin' up PW's backend. Currently PW doesn't make many assumptions about previous expertise of the developer who uses it and requires very traditional skillset apart from jQuery which knowledge is de-facto standard for any front-end developer. And this fact is the key concept that makes PW open and friendly for everyone. The thing is, people still can use BEM OSCSS or whatever they want if they build with PW as it's a framework as much as it's a CMS. You can use existing backend and build on it or even start from scratch if needed. You can use any framework but you're not forced to do it. I don't think current default back-end needs loading optimization at the moment. PW has one of the fastest backends I've ever seen. IMO, optimization at this point would be premature and profit would not be worth the effort. BEM and OSCSS (don't know about SMACSS) are templating ideologies aimed mostly at large projects with big dev teams. Yandex, the largest Russian search engine company (kind of little-scale Russian Google) who invented BEM, use it in their projects because they need it for their very complex and unique projects. They wanted to shorten render time of their interfaces in (mostly) older browsers and to standardize the way their teams worked. These problems are very rare for most projects. So modular CSS, IMO, is a marginal demand. MODX made a big mistake putting their chips on ExtJS in the back-end of Revo branch. They lost many loyal devs since then. Partly because this framework was marginal at the market and its learning curve was steep. Let's not step on the same rake. Not sure but I guess modular JavaScript could be added optionally via a module. The strength of PW is its openness to any developer and, I dare to say, any user. It was a relief for me to see PW's interface. I'm not sure PW has to compete with these systems as (for me) it already has a better interface. Less noise, less distraction, less confusion = more focus, more flow, more get done. Accessability is a good point. I think this kind of interface extension could be implemented as a module. Btw, I believe BEM and semantic markup ideologies are not compatible As far as I know there is a project for core testing in PW, but not sure if it's active. Ryan can tell for sure. I'm inclined to think that PW's default backend should stay as slim as possible in terms of dependancy on third party frameworks and concepts but be as extensible and hookable as possible. Every new "hard-coded" concept or framework will bring new element of complexity to a system, make it more closed, and make learning it more difficult. All these features proposed here are really great and PW will definitely win more developers and users if it implements at least some of them. But, IMO, they have to extend or override PW's defaults not substitute them. Another way is to start an alternative backend project that would embody the latest tendencies of front(back)end development and help make some hype in more visually-oriented and framework-aware crowd.
  16. slkwrm

    Pirate Maps!

    Wow, Pete! This walking puzzle thing is approachable only for Einstein-level minds
  17. Hi, Totoff. You have to add title to valid attributes of <a> tag. You can find this option on the "input" tab of your text field -> TinyMCE configuration -> valid_elements. Find <a> attribute and add title to it: a[href|target|name|title].
  18. Hi, Harmster. Your explanation is a bit vague in terms of what you want to achieve on a conceptual level. Where do you want to place your code? What is the relation between fellow player and user1/user2? Are fellow players users? What about summoner?) These questions, while may seem a bit excessive, will exclude double-meaning and help others get your idea more easily. (and you will get help quicker )
  19. You can do something like this: echo "The next article is:"; $id = 0; //check if there's this month next article if ($id = $page->next->id); //check if there's next month article elseif (count($page->parent->next->children)) { $id = $page->parent->next->children->first()->id; } //heck if there's next year article elseif (count($page->parent->parent->next->children)) { if (count($page->parent->parent->next->children->first()->children)) { $id = $page->parent->parent->next->children->first()->children->first()->id; } } if (!$id) echo "This is the end my friend."; else { $p = $pages->get($id); echo "<br /><a href='{$p->url}'>{$p->title}</a>"; } You have to put this code in your article template. It suggests that you don't have month pages without articles. Kongondo is totally right that you have to be comfortable with PHP, HTML, CSS at least at the beginner's level to enjoy the benefits of ProcessWire. ProcessWire propels experimentation and creativity so you could go ahead and modify the code for finding previous articles as your homework
  20. Well, maybe it's a bug. I don't have more ideas here
  21. Hmm.. that's weird. Does your newly created page have a title after the script throws the error? Try to save your page twice in your function: at first with only default title and then with a title in Russian (or save this title field separately). Just to test it. No idea why you have this error. Maybe someone more experienced could help with this.
  22. Hi, Valan. Try to sanitize your selector value: $sanitizer->selectorValue($value). If you're using Russian language in your titles I guess you can easily exceed the requirement for the selector string of being less then 100 symbols. Are you sure you have to look for the existing category by its title and not be the page name?
  23. @ranzwertig I'm pretty sure the problem is with your strtolower() function. You should use mb_strtolower() instead. Make sure you have --enable-mbstring option activated. Here are the instructions.
  24. This one will refresh your css automatically every time it's updated (works only in a server environment): http://cssrefresh.frebsite.nl/
  • Create New...