pandaman

Members
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

2 Neutral

About pandaman

  • Rank
    Newbie
  1. Hi, everyone! I'm going to start a new nice site, but the client wanted absolutely a site like one he found surfing the web. It has a smart navigation system, like an app, so you won't find "jumps" between the pages. It's super cool and i found it uses page.js as client-side routing, loading the main content with ajax calls. So, this is my question. Do you think i will find some problem using this script, or maybe i'll find some conflicts with processwire internal routing? Maybe here there is someone who already used this type of client-side routing with PW? I'd lile to use PW, with many different page templates...
  2. I can't thank you enough @jmartsch !!! These are the kind of problems I'm sure I would encounter doing this job. It's a great start! If I find any problem dealing with this job, I'll let you know... Thank you again
  3. Because a real e-commerce, with prices different for each group of customers, offers, world VATS managing, etc deserves a SOLID solutions, and we always worked with Magento.
  4. A new client asked for a an e-commerce (and we usually use Magento), but with a lot of customizations, blog, posts and other cms stuff. Magento sucks for these kind of operations, and i'd like to integrate Processwire in this adventure. In the last months i appreciated a lot PW and i made all my sites with it. So i'd like to have a regular cms part, with pages, news, etc... and the shop part, sharing the same html layout. Have you ever tried to work with this 2 solutions together? Any advice to avoid conflicts?
  5. Sorry for the long title, but it explains well my doubt: for a corporate site, with all the pages looking the same, like the Skyscrapers demo, i know how to work. But usually i did simple sites for little clients (with 1 or 2 languages), where creativity is most important of the content. I moved to Processwire, from Wordpress, because maintining is a time-consuming operation and i wanted something "easier", especially when clients ask for new functionalities to integrate. Something like this site http://kl-webmedia.com/demo/owkey/index.html I worked with WP for years, sometimes i used third-party templates, and i started to work writing the HTML code in the body of the posts/pages. That was the way, more or less, in Wordpress. Now i'm using Processwire, and i used the same method. I created some fields, based on a textarea (not the body one used in the demo, because i don't need the text editor), inside a main template. So, the main content is managed inside PW pages backend. if you have to do the same site i linked, do you use the same method, or do you put the html in a template php file, and create inside PW a template for each page? Because every page have a lot of different tags and divs, with parallax, containers, big photo, fancy graphics, and i don't undestand if is easier managing the code inside PW, or outside in the php files (making all the text a translatable string). It's a simple question, with a lot of different answers, all correct
  6. Thank you. Just for the record, it's not "tag" but "tags". $tagsarray = array_unique($page->images->explode("tags"));
  7. Hi! I'ts my first post here and i say hello to everyone. I've just started learning Processwire, but i love it so much! It's so simple (and deep), that after a lot of years on Wordpress, it seems incredible to me to create great sites without a headache! By the way, i'm creating a gallery page in my first processwire site, using the default images field. I activated the tags on that field (tag for the images, not for the field), to have a simple taxonomy. I need to read all those tags once (for that page), and i wrote something like foreach($page->images as $tag) { $tagsarray[] = $tag->tags; } $tagsarray = array_unique($tagsarray); foreach($tagsarray as $tag) { echo "<div class='filter-item wow fadeInUp' data-wow-delay='.1s' data-filter='{$tag}'>{$tag}</div>"; } It works, but i bet there is a shorter API trick. Am i right? I read something about a->unique() function...