Jump to content

Search the Community

Showing results for tags 'templates'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 85 results

  1. Hi awesome Processwire folks, I want to make custom processwire admin views. For example, let's say I wanted to create a top level section in the PW admin for managing videos. And I want to use a data grid (just for examples sake... I would probably design a good layout for this - something effective and easy to use)... I know how to add pages to the admin interface by adding them in the page tree, pretty straight forward. The problem is, I am really having a hard time understanding the admin.php template and how the ajax call, methods work. To be honest, I have made a few attempts to modify the behaviors etc in this file with little success. I don't quite understand how processes work at all in PW. I read the classes and it can be over my head in some cases. Does anyone have any suggestions about how I can get my head around this and how I can really start taking advantage of PW to build out some more complex PW admin functionality... any suggestions at all. Thanks in advance,
  2. Since everyone (mostly) are nattering on about responsive templates of one sort or another, though you all might be interested in this little article that I found giving a rough sum up of a pile of responsive frameworks. Not all, by any means, but not a bad little collection: http://designshack.net/articles/css/which-is-right-for-me-22-responsive-css-frameworks-and-boilerplates-explained/ Joss
  3. Hi, I'd like to have an "edit" option for pages in the frontend. I thought I could append an urlSegment to the page url and (instead of coding show and edit functions into one template) simply switch templates: if($input->urlSegments[1] == 'edit') $page->template=$templates->get('page_edit'); This code doesn't work ... Is this even possible or do I need to redirect or put all code in one template? Thanks! thomas
  4. Hi I am pretty new to processwire and it is really growing on me, even though I am not a programmer. One of the things I really appreciate is the freedom and simplicity of the administration structure. However, I think there are a couple of things that could help navigation, and one of those is categorization of templates and fields. This is not intended to be categories for the layout of the site or categorization of data, but simply an optional way of keeping things sorted in the backend if the site gets a bit on the large size. In affect, it would just add another way of sorting fields and templates. For instance, you may want to group fields together that are associated with a repeater, or you may want to group fields together that you tend to use as all-purpose fields like "title" and "image" Anything you wanted really. For many sites, this might be a little bit of overkill, but if a site has a huge number of fields or templates, then this could be useful. Not a major request, just a "nice to have" sort of thing. Joss
  5. I wonder how different people handles different "file structures" for templates. I know that you can only put php code inside a template files, and i have thought that when you have to create a lot of unique "pages" with different php code it will take time to create a template file for each page. Not only that, but eventually, if you create a lot of templates, the templates folder would get very crowded. I was looking for a better way to organize my php files and found this solution. Instead of creating a template for each unique page with custom php code, I just create a single template named "include". This template just has two fields: title and include_path. The code of this template is just: <?php include $page->include_path; ?> In the "include_path" field I set the relative path for including other php files, and this method gives me a more organized collection of php files nested in various folders. For example, for a form called "reservation", I would just create a page with the template "include", and the field "include_path" set to "./php/forms/reservation.php". An example of this file structure: site/ --templates/ -----/styles -----/scripts -----/php --------/forms --------/processes --------/catalogs --------/galleries -----head.inc -----foot.inc -----home.php -----blog-post.php -----include.php Do anyone know if there is a better way to handle php files? o anybody would share their file structure approach?
  6. Hi, Just moved a dev PW install to another domain and found that 1) I couldn't move with it creating PHP errors with a straight move of files and DB. 2) I tried a fresh install updating the admin and then adding the new template but the admin -> setup -> template isn't displaying drop and drag handles so I ccant administrator it at all (see the attached image). any help would be amazing!
  7. Hi there, I want to use Bootstrap with my templates. This may seem a very obvious question but am I correct to assume that you simply add the various Bootstrap folders in to the PW templates folder? Normally, the pathing in Bootstrap is relative to the location of the page(s) in the site structure. However, I am unsure how PW utilises the template folder when pages are actually being served. I hope you understand what I am trying to say here Any thoughts around this one would be appreciated! Thanks --Gary
  8. Hi guys, I have been playing around with multisite recently and wondered - what would be the best way to share some template logic between multisite instances? I have an upcoming project where two different sites would have different users and setups etc but they need to share some basic similarities in look and functionality. I was thinking of setting up the sites as separate sites under multisite and then finding a way of sharing something such as a 'main.php' file that each template calls. I would also like to share a 'base.css' file between the sites as well. I want to do things this way because they want the potential to be able to expand into more sites over time - up to 5 or so. What would be the best way of doing this? Thanks in advance.
  9. When I for example generate a list of articles, I get my pageArray through the API within another page’s template, iterate through it and call the render method for output. Works great. But what to do if I wanted to make the template of these articles behave in a certain manner depending on the the context (the current page’s template) the render method is called from? Is there a way to access the vars existing within the current page’s template or even the current page’s field values on rendering from the articles’ template? To check “Am I rendered within/from another page’s template?” and “Is the var $xy or the field ‘ab’ set to ‘brabra’ in the other page I’m rendered in/from?”
  10. Hello all advanced users (Ryan, Antti, ?) Introduction: I am curious about how the template files get included, called, how they are run and such. Last week or so, I tried to create little MVC (or rather, V(C+M) ) directory skeleton, where templates itself would be classes generating data for 'views', which would be located in one of the directories in '/site/templates/'. However, when I set up Base class, set few of my templates to use this, added View object (which in theory loads file and dumps data in it), prepared some place for common functions, and prepared autorendering in snippets (creating renderXyz function would give the template object variable called $Xyz with generated object/array of objects). However, upon doing all of this, system felt really slow-ish, having generation time 0,5s-1s for localhost and simple, 3 or 4 field pages, which felt really unnatural - and I suspect my noobish object model So this brings me to my question: I noticed that there are TemplateFile objects, with render() function, and such, whole ProcessWire is 100% OOPhp, is there any recommended way I can use ProcessWire as any MVC framework, having autoloading, so I don't have to use require(); with objects for instance? If this doesn't make any sense for you, I'll try rephrase later, but I hope it does make sense.
  • Create New...