Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/02/2014 in all areas

  1. I want to like this post multiple times but the forum software doesn't allow me to do that. So: Like. Like. Like. Like. Like. Like. Like. Like. Like. Like. Like. Like. Like. Like. Like. Like. Honestly: It's comparing apples to oranges. PW is strong. It is the most intuitive, the best designed (in terms of API and UI) CMS out there with the smallest footprint possible. I recently used again the multi language support. I mean, look at the API. Look at the solution for a problem each CMS has. It is just beautiful. You have several ways to solve that problem (as always with PW). But it is there, written in the core, well documented on one(!) API page, because it just works intuitively, it is just simple. Every addition to the core is an addition which solves general problems and the way Ryan solves them is just genius. There is no addition you have to scratch your head when reading the new API. You always think: "wow, clever". And this is the way to go with the core. Make it simple, make it smart, make it beautiful! Regarding themes, profiles and such: It is already possible. It is out there. Provide a custom profile for a real estate agent: Give him a set of modules, fields and templates to handle his offers. This is no problem! This is even easier and more flexible than it ever will be in WordPress, because it goes way beyond a custom theme and can be installed with one click. But: Nobody will care at the moment, because ProcessWire has no own category in theme/template websites, because ProcessWire has not the attention of other plug&play systems. And this is totally okay! Think of TYPO3, a widely spread system, mostly used in enterprise environments and even on small sites (dunno why), but the point is: Everyone (at least in Europe) knows it, it is one of the most used systems in the business sector (not on private children soccer club websites). But: this is the goal! Be the system developers use. Don't be the system every idiot wants to use. Concentrate on performance, flexibility and most of all: beauty of the API! The rest will follow.
    7 points
  2. Welcome to the forum bipster! For the projects in our website (see my signature) I used a table field and works very well I created three templates: paragraph, images and video, and added them to the table field "content" These are the fields in each template: paragraph: text (textarea) images: is_slider (checkbox), images (image) video: mp4 (file), webm (file), poster (image) on each template I put the code for rendering each object, for example, the video template is like this: //video.php (simplified) <div class="video"> <video muted poster="<?=$page->poster->url?>"> <source src="<?=$page->webm->url?>" type="video/webm"> <source src="<?=$page->mp4->url?>" type="video/mp4"> <p>bad browser, no video for you!</p> </video> </div> and on the project pages I output all the content simply with: foreach($page->content as $c) { echo $c->render(); }
    4 points
  3. Is ProcessWire A Viable WordPress Alternative? Apparently we've being noticed by the WordPress community.. not entirely sure if that's good or bad thing
    3 points
  4. You should try to have major version in sync, PHP should be both 5.3 or 5.4 Also the minimum requirements for PW are: (not 5.0.10 or 5.0.8) regarding 5.0.8 see also: https://processwire.com/talk/topic/7034-check-for-new-modules-causes-internal-server-error/
    2 points
  5. Hello, I created a simple REST helper in order to create REST APIs with Processwire, without depending on external routers Here you go!. https://gist.github.com/clsource/dc7be74afcbfc5fe752c
    1 point
  6. Hi forum, I got a new one online last week: www.ecotec.de A fully responsive website for a German consulting firm specialized in cost-cutting strategies for industries with high energy consumption. Again based on my - evolved - Unsemantic Site Profile which allows for responsive sites compatible down to IE7. The site incorporates a former stand-alone WP blog which has been integrated into the new site. For this I used the new Migrator and Wordpess Migrator modules and got grandiose personal support from adrian and nico. Thank you guys, you were extremely helpful and patient. Other modules used: Admin Save Actions AIOM+ Email Obfuscator Markup Simple Navigation and Superfish flyout navigation (not a PW module) However, though I learned a lot from this project and improved my coding skills, I didn't fall in love with the site. In particular I'm unhappy with the purple/gray color scheme. Originally the project scope included a - soft - redesign of the brand appearance. But while the process was ongoing, my client somehow realized that he was still in love with his logo, his Futura font (buh!) and his purple primary color (buh, buh!). We had some very tough discussions about this in the middle of the project, but what can you do? At the end, here we are: in a purple dream. I hope I made the best out of it. One last thing (no, not what you think): The front page doesn't validate. The validator claims open elements in the blog posts section of the front page. For heaven's sake, I can't find an error in my code. So, if someone finds out why, please let me know. Cheers
    1 point
  7. Hi guys, As some of you know I'm part of the Milktop team, but strategically we decided to go back to the format we had one year ago and recover ED Design, my collaboration with Erika. Today we are launching our website. http://ed-works.com/ This is a soft launch only for the PW community because I trust that this is the best place possible to have a site tested I hope soon I can write a case study. Hope you guys like it! (still some work to be done concerning SEO and accessibility)
    1 point
  8. 1 point
  9. Thanks for your suggestions!! As I said previously, I'm a newbie to all this, so your help is very much appreciated!
    1 point
  10. Hi Nico It's not the version of PHP that's potentially the issue. It's the fact the plugin now uses the "requires" line. IIRC that's a pretty recent PW thing - possibly dev branch or post 2.4 at least (I'm not sure on the exact version.) If commenting out that line fixes the problem I'll amend the module page to reflect the correct compatibility.
    1 point
  11. Thanks Nico - I'll take a look
    1 point
  12. You could use my QuickTags editor. TAB key support is planned.
    1 point
  13. There were indeed two corrupted images. The originals were almost 10 Mb. I already adviced my client that images of that size are not ideal for a website. It seems now oke. Thanks.
    1 point
  14. new german updates for actual PW dev 2.4.10 (02 August 2014). Zip contains only updated/added files (in comparison to the default 2.4 lang pack). updated files: wire--modules--fieldtype--fieldtypepage-module.json wire--modules--process--processrole--processrole-module.json added files: wire--modules--fieldtype--fieldtypeselector-module.json pw-lang-de-dev-update.zip
    1 point
  15. My 2 cents, and sorry if I'm repeating things that have already been said – didn't have the time to read everything already posted here. Wordpress has become vastly popular as a blog system. It is being used by a gazillion of people worldwide, most of them not very tech-savvy, which is why there is a huge market for prefabricated themes and plugins. It started out as a small open source project, but is now – at least partially – being developed by a company with about 250 employees plus a very active community of freelance developers. Due to its huge popularity, it has morphed into a system which can also be used as a CMS. This exponential growth into the most popular content publishing system worldwide has taken it's toll. It's bloated, there are unmaintained plugins, it has security issues and if you look closely, the sheer number of themes and plugins does not necessarily say much about their quality. (Did I just hear someone say “Windows”? Nevermind.) ProcessWire is a content management framework/system which was originally developed by a single developer. The community is picking up lately with more people developing plugins as well as contributing to the core while the system also gains traction with a small, but loyal user community. It's clearly not a system for everyone, mostly based on the design of the system. It might never become a system for end users, but obviously it has become rather popular among developers looking for certain features in a CMF/CMS. Why anyone would seriously want to compare both systems is beyond me.
    1 point
  16. @reems: if there are all images already created, the imagesizer get not involved. I bet there are not all imagevariations created now. But 30 seconds is far to long for only 80 images. Maybe there is one corrupted image in or what ever. To get rid on it you may debug on which imagefiles it is called. This way you can track down the issue, I hope. If you have this on your local host you simply can add a line into the imagesizer file here, at the start of the resize function: $logentry = $this->filename; wire('log')->save( "debug_resizes", $logentry); This way you get a list in site/assets/logs/debug_resizes.txt with all filenames on which the imagesizer is called. (site/assets/logs/ must be writeable, what it should be by default) Just empty or delete the logfile if it contains previous entries and call your admin page that causes the issue only once and inspect the logfile afterwards. If you need further assistance come back please.
    1 point
  17. I won't tell to much but I'm currently working on a theme module anyway. Website is already kind of ready: http://processthemes.com/ But I think we all should agree on at least one thing: ProcessWire should never integrate a real theme engine in it's core. never.
    1 point
  18. Take a look in the Troubleshooting Guide: http://processwire.com/docs/tutorials/troubleshooting-guide/page3
    1 point
  19. Hi i just finished website that i build on processwire. Im a frontend developer and noob with php. But with processwire i managed to build this site, so i want to thank you for giving us such a great tool for building websites. Here is website in Polish, and in a month or so i will release english version of the site. http://hejtuje.com english version will be avaible in here : http://hate.it Some feedback would be nice . Thanks PW!.
    1 point
  20. Hi sorry was busy. So the main idea is to give people the ability to say whats frustrating them, not only in the world but also localy. We have Categories like politics,sport etc. and town's (larger towns in Poland). User need to register to vote or to create new issue. On forum we can find some examples of user register forms. I used the one which creates user and page. This way i can easyly show users posts like this : http://hejtuje.com/members/vxda/ Also when user register there is confirmation email sent to user. If user will not confirm there is a lazycron module every couple of hours that deletes each user that didnt confirmed his email. There is also a way to register and login via facebook. For that i used apesia module : http://modules.processwire.com/modules/facebook-login/ . I changed it a bit so that when user registers with form, he can also login with facebook and it merges into one account. User can choose to stay lagged in, for that i used plugin made by craig-a-rodway http://modules.processwire.com/modules/login-persist/ User creates issue: basicly used guides from forum, its quite easy to allow members to create pages. I used adrian's module for grabbing thumbs from video's: http://modules.processwire.com/modules/process-get-video-thumbs/ For vote system i acculy asked my firend php programmer and he did that one for me. For comments we used disqus. Had some problems with SSO (single sign on) so here another friend helped me out. This way whenever user register/login it automaticly creates account on disqus and log user in (no need to register on site and disqus separately). To make it a bit more fiendly for user i also detect from which city user is visiting website, then im comparing result with cities i got on my website, if there is a match im showing the first issue from that city on home page. If not showing the first issue from capital. whats next ... humm there is quite alot of jquery and ajax. If u got any questions please ask il try to answer them best i can. Here are some topic's i made during development: https://processwire.com/talk/topic/6763-lazy-cron-problem/ https://processwire.com/talk/topic/6619-login-user-without-his-pass/ https://processwire.com/talk/topic/6562-sending-email-after-moving-page-from-one-parent-to-another/ Cheers
    1 point
  21. I think this is most likely the case, assuming you do have multiple render() calls. Your _init.php may not be the right place to do some of this stuff, or if it is, then you may need to add additional check so that you don't have the same things being run twice. For instance, you have a $config->scripts->removeAll(). If you add some scripts to $config->scripts, and later have another $page->render() call, then the files you previously added to it would again be removed by your $config->scripts->removeAll(). There are a couple ways you could solve this. First would be to just move your code that shouldn't be run twice to a separate include file, and then use PHP's include_once() function on that file. For instance, your _init.php could have this: include_once("./_init_once.php"); The above is the safest bet, because if your _init.php defines any functions or classes, then you don't have to worry about them being defined twice (and resulting in a fatal error). But if you want to keep everything in your _init.php, you could do this: if(!defined("LOADED")) { define("LOADED", true); // your code here // ... } Lastly, I wanted to mention that your files will have access to an $options variable, which has a 'pageStack' property containing a stack (array) of pages that initiated the current render. It will be empty the current render() is not recursive. So you could accomplish the same thing as above like this: if(empty($options['pageStack'])) { // your code here // ... } One more thing I just remembered is that you could also tell your render() call to skip the prependTemplateFile: echo $somePage->render(array('prependFile' => ''));
    1 point
  22. You can make a simple WireData module to put functions specific to your project you can do all sorts of things like hooks, your own helper markup generating functions for use in template or other modules, or whatever else. See the HelloWorld.module that comes with the default profile. It comes down much to preference but I do that often, and instead of including a functions.php in template it will be available everywhere. You could even go as far as setting a new API var for use in the system. In the init() of such a autoload module you would call: $this->set->fuel("projects", $this); And you'd have a $projects API var that you could call methods from your class. Or set properties to existing API vars to maybe have a $user->fullname. Possibilities are endless.
    1 point
  23. Welcome to the forums abe.izar. Seems like they should make json_encode at least attempt to typecast an object to a string (which would convert to IDs here). Maybe I can update wireEncodeJSON (a front-end to json_encode) do that. However, if you really want to export pages and all their data to JSON, here's how you can do it: function pagesToJSON(PageArray $items) { $a = array(); foreach($items as $item) { $a[] = pageToArray($item); } return json_encode($a); } function pageToArray(Page $page) { $outputFormatting = $page->outputFormatting; $page->setOutputFormatting(false); $data = array( 'id' => $page->id, 'parent_id' => $page->parent_id, 'templates_id' => $page->templates_id, 'name' => $page->name, 'status' => $page->status, 'sort' => $page->sort, 'sortfield' => $page->sortfield, 'numChildren' => $page->numChildren, 'template' => $page->template->name, 'parent' => $page->parent->path, 'data' => array(), ); foreach($page->template->fieldgroup as $field) { if($field->type instanceof FieldtypeFieldsetOpen) continue; $value = $page->get($field->name); $data['data'][$field->name] = $field->type->sleepValue($page, $field, $value); } $page->setOutputFormatting($outputFormatting); return $data; }
    1 point
×
×
  • Create New...