Jump to content

Philipp

Members
  • Posts

    198
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Philipp

  1. Your're looking at the page tree of ProcessWire. It represents the structure you also see on the page itself. As you mentioned, the first Page (/) with the house icon is the start site. You can't delete this page, because everything within PW is a child of this (even the admin pages itself).

    In the default installation, this page has the template "home". You could change this but you don't have to (and also it will cause trouble with permissions...).

    In the PW admin, go to Setup->Templates to change the fields of the home template. Open Setup->Fields to edit or add new fields you want to use in the home template. We can find the template file for home under the template directory in the PW installation path: /site/templates/home.php . Open it and you will see the markup for the start page. As in the tutorials, you can change everything here and build your own customized start page.

    Basically, you just overwrite the default home template with your own fields and templatefile.

    You could try to just download the blank profile  and instead of installing a fresh PW, just replace the content of the site/templates folder. After that, you can delete all example pages from the admin and customize the home template.

    • Like 7
  2. I'm note sure if it is possible to "reset" the config for a single template.

    You can check, if the page is requested via AJAX. In your prepended php, add a if-statement like:

    if($config->ajax == false ) {
    // Your init.php or code ...
    }
    //Nothing happens if it is an ajax request.
    

    The file will still be appended but this time no code or markup will be added. The $config->ajax is a PW function which is set to true, if it is an AJAX JS Request.

    • Like 1
  3. Maybe we can make the base color adjustable. A single line of CSS or a line in $config. Here are the only PW blue, green or black versions:

    post-752-0-47497700-1378321655_thumb.pngpost-752-0-44167900-1378321658_thumb.pngpost-752-0-76670500-1378321660_thumb.png

    I wouldn't make the topic more complicated than it is. We can right now customize the admin theme and write modules. This discussion is good, because we ould create some interessting ideas for future modules - build for the backend of PW.

    The idea of a blank admin theme is great. This could be layed out as a kit to develop your own admin theme. (In addition, PW could ship with a theme created on top of this blank master). 

    • Like 7
  4. Update.

    post-752-0-99921600-1378314188_thumb.pngpost-752-0-80192400-1378314191_thumb.png

    • Font size is now 14px for all base fonts, heading/nav are mostly 16px. 
    • Sidebar action shrink down. I think we now have enough space for most page trees.
    • Removed the boxes around the fields as suggested by apeisa. Thin lines to seperate them, especially the multi-column fields. Not sure about this one, because it' really defines the "look" of the PW admin.
    • Updated setup view added.

    Now looking forward to do more on those fields. Repeaters and image uploads, fieldset. 

    Note: You can use this design under a Creative Commons BY-SA 3.0 licence. Of course, the ProcessWire logo is owned by Ryan Cramer and the Icons are taken from Entypo. Contact me, if you want the layered files or sliced graphics.

    • Like 9
  5. To justify the optional sidebar:

    Screens under 1200px will not see the sidebar. It will be hidden by default.

    I've set the first offset margin to 15px and then increase the margin by 20px each level.

    On a 1280px Screen with 1/3 sidebar I get around 425px.

    On a 1920px Screen (24" HD Office) I will have 640px for the sidebar.

    The "problem" are different lenghts for the text + the edit|view|new buttons. Question: How many sublevels do you usually have?

    Bigger text and iconography are exactly what I dislike in this solution. I think the default admin makes a great job at being minimalistic (not in a trendy, but in a practical sense) and very usable. In my opinion Icons are distracting.

    I like that aspect. In the next version of the concept I've stripped down some icons. I'm using them for arrows and the template type of a page. I think, it's the tiniest way to display the "type" of template of a page.If not, my customer just thinks of pages and not of galeries,blog posts, news, products,...

    The top bar is now white. I've chosen the pink/magenta color for everything that has an action, the blue colorto indicate things. The font size also went done from 18px to 16px and the overall look is now a little bit more compact.

    post-752-0-64083200-1378155312_thumb.pngpost-752-0-08114900-1378155316_thumb.png

    The second screenshot demonstrates a 1280px window size.  

     

    A while back I was toying with the idea of creating a skeleton admin theme, a sort of admin starter kit. A simple black and white stripped down theme with heavily commented CSS , maybe with a few CSS options to move some stuff around, e.g. tree on left, tree on right etc but with the jQuery working as normal.

    This would be a great start. Especially with the theme switcher for the upcomming versions. We could quick build a custom view for a client.

    Another thing to the "Admin Kit". Maybe the admin-themes can get some sort of an option page where we can disable things like the sidebar. Not sure about this one...

    • Like 6
  6. Thanks for the feedback.

    The default admin theme needed to be something that could scale near infinitely, and delegating the page tree to a sidebar introduces a lot of natural limitations (though none that scrollbars can't solve, but I'm not a fan of them). Another goal was to keep the user focused on the page they are editing by having the browse and edit states be very separate things. Lastly was the issue of overhead: generating a page tree involves a lot of work, and can contribute to making the admin feel slow… especially if having to generate it for every page edit. (Though this may be something caching could solve, but it could be tricky to develop: clearing such a cache after each page save might defeat the purpose). I did actually test out both SilverStripe and MODX before developing ProcessWire–I wasn't pleased with their page trees and really wanted to differentiate ourselves from that. Though your design here for the page tree does do that–it looks a whole lot better than what's in other systems.

    I agree with you, Ryan. PW is focused on scalability and a simple interface. Pressing the page tree into a sidebar could cause scrollbars. And I'm not sure how to handle the client side AJAX while maintain a good site performance.
    ProcessWire has this zen focus, because there are not so much buttons, not 4 positions for links or three submenu levels. Showing only one view (edit page, page tree, create page) is really good. But sometimes when the tree collapses because I've took the "wrong " way back from editing a page it becomes anoying.
    The concept should always leave the option, to just use this "pure" editing by hiding the page tree.
     

    In my pre-PW work I've done a lot of custom admin pages for clients to use. It really pays to keep these very focused on application-specific work flow, terminology, etc. I don't expect clients to accept the level of abstraction necessary to work directly with the PW data. The admin pages provided by core should be a tech tool, guaranteed to be scalable and capable of accessing anything any application might have. Sure, there's room for improvement but what about putting that effort into easing the task of constructing a more focused and mediated admin interface for clients to use.

    But this would add another layer of abstraction to the site. A page tree is different to e.g. a bucket of blog posts as seen in Wordpress. I know, sometimes we build sites that have a slightly different structure on the front-end or we need to fit the internal workflows to the CMS admin panel while having a completely different front-end.
    Ryan wrote something on this here: http://gadgetopia.com/post/7242 (go to the comments)

    I haven't looked deeply at how the admin pages work now but given the modular way things tend to be done in PW I'd think we could do something to streamline the building of custom admin pages. Sort of an admin construction kit. Let the client deal with "skyscrapers" and "cities" rather than "pages" even though underneath, they are all PW pages. Reuse the basic underlying CRUD while adding application specific prompting and tools to help the user with the more focused task of working on a city, skyscraper, category, etc. Build a custom interface where clients can do their routine tasks easily. if they end up with an odbball situation beyond the scope of what you built for them you can always talk them through using the standard admin interface, and if that becomes a habit you extend their custom interface.

    Eam admin pages. Sort of an admin construction kit. Let the client deal with "skyscrapers" and "cities" rather than "pages" even though underneath, they are all PW pages. Reuse the basic underlying CRUD while adding application specific prompting and tools to help the user with the more focused task of working on a city, skyscraper, category, etc. Build a custom interface where clients can do their routine tasks easily. if they end up with an odbball situation beyond the scope of what you built for them you can always talk them through using the standard admin interface, and if that becomes a habit you extend their custom interface.
     
    Personally, I don't think a single admin interface is ever going to be optimal for both programmer and client. Those are different audiences with different needs. I'd be wary of anything that compromises the ability of the standard admin pages to deal with huge 

    The admin construction kit sounds really good - especially when multiple admin themes become a default feature of PW(v2.5?). I'm not sure about the hard split between developers and customers. Maybe only a slim version of the admin theme would be enough?

  7. Thanks for your feedback. 

    @diogo I'm mostly a designer, not a programmer. I currently have no plan or experience to code this concept.

    It would be nice, if the right side of the screen would load dynamically via AJAX. There was a concept with Lightboxes loading the admin views but we would have the right div insteaf od a popup. Additionally,we have to make sure, that the URLs are right.( HTML5 History pushState?).

    I'll post some alternatives color schemes later.

  8. Two days ago, an idea about a new admin theme came to my mind. Some hours later, I've crafted a first concept in Adobe Fireworks....

    The look and feel of the admin is important

    Two months ago, I've introduced some teachers into ProcessWire. They were none-technically people. At the end, they knew how to use the admin panel to create content or update a gallery on their new page. However at some points, they got confused with parts of the admin theme -beside the problems with our concept on how to use fields and templates for creating content.

    I think one factor why Wordpress became so large, was the great Adminpanel. It works well and easy (as long as you have a blog and not a twenty-plugins-for-text-pages-site). Editing content on a daily basis is the main task of my customer. I've to take this aspect serious.

    Problems I wanted to solve

    • Have the page tree always visible. If I do not click the right link, it will be closed after I've finished editing my site
    • More visuals like icons.
    • Simplify some workflows. Creating 3 or 4 pages can result in multiple unnecessary clicks.
    • More focus on important links like the tabs.
    • Guide my customer through some action. Help them to repeat simple tasks.

    The concept

    First: Nothing is perfect and its not possible to find one single solution for everything. This was just done in a couple of hours and it's only the first iteration.

    post-752-0-87829100-1378054725_thumb.pngpost-752-0-04309700-1378056665_thumb.pngpost-752-0-79546100-1378056895_thumb.png

    Quick action button

    Next to the ProcessWire logo is the quick "Quick Actions" button. It should be possible, to configure it like: "Create a new Page with Template X with page Y as a parent". Use it for skyscrapers, news or galleries. (Yes i know, the arrow is pointing upwards. This is wrong)

    Two column layout

    The page tree is always visible (as long as we are in the pages view). It can be navigated as the normal page-tree. If you click "edit" it will become highlighted. Every action that would take you to a new page, would be displayed in the other half of the monitor. Speaking of a "half monitor" - I think that most people use a screen resolution of atleast 1300px. The sidebar should take up to 1/3 of this. On smaller screens, it will become hidden by default or we just simply step back to single pages for each view. If the content is to long, the sidebar becomes scrollable.

    Page tree

    I like the Template Decorator made by mindplay.dk. It fits the concept well with black outline icons for every type of template. The same icons could be used in the Quick action menu. I'm note sure what to do with the "move" action. 

    To Do list

    • Think more about the behavior of the elements. 
    • Design the modules view. 
    • Rework the search and the top menu.
    • Options to "brand" the panel for agencies while keeping the ProcessWire logos.
    • What happens if we are on mobile (small screen) devices?
    • Listen to your feedback.
    • Like 29
  9. Thanks.

    I know that sometimes the Yahoo API takes it time. Does it work now or does it work on the jQuery Plugin demo page?

    @totoff: The violet and the red are the clubs colors. I agree with you, they are not great but using the red for large areas like the violet wouldn't have been a better choice.

  10. Today I just want to show a new page build with ProcessWire. It's nothing fancy but the client is more than happy.

    http://www.rv-heidenheim.de (german content)

    The local horse club had an old ugly Flashwebsite which we relaced with a fresh and modern PW site. The goal was to create an easy system to maintain content and to inform people about the club. 

    Behind the scenes:

    • Processwire with ProCache let the site run faster than any horse in the barn.
    • Using the PageLink Field to create a menu structur.
    • Skeletton 960px grid but right now we removed the mediaqueries. We will add the mobile view later.
    • The weater widget uses this jQuery plugin.
    • All widgets in the sidebar are pages and fully configurable by the backend user.
    • A year ago, this was my first Processwire page. But it was never released and we made a complete new second version last month.
    • First time I've used an icon font. Try fontello.com to build your own icon font.

    The site was designed on a friday evening and only 24 hours later the whole site was done. Using PW it's just a charm to build such small sites and let people insert their content.

    • Like 5
  11. Thanks for the module. 

    I've got a problem with the data fetched from Piwik.

    http://d.pr/i/vTlo

    My visitors don't stay on the site for 3 days. The value should be (looking on the piwik panel) around 2 minutes. Maybe this bug is caused by the following lines in the .module file:

                case 'avg_time_on_site':
                  $visitTime = $this->piwik->getSumVisitsLengthPretty();
                  $value = $visitTime['value'];
    
  12. I think the latest version stills creates a folder for every page. But there is a module that fixes this behaviour if you have problems with those folders.

    You don't have to think about the folders when moving a site. They are namend after the unique page ID, for example /site/assets/files/<pageid>/myfile.png . The folder name might not be "friendly" but your file name remains the same as uploaded (a second file with the same name would get a number). 

    Alles pages are "rendered" when a visitors visits your site(so PHP and the DB is involved). You can purchase Ryans ProCache module. This generates static files and speeds up your site. It really configurable and works perfect with the PW build in functions like URL Segments or Pagination.

  13. Two possible ways to do this:

    1) Use the Site Profile Exporter

    Just install it on the local installation, run it and then install Processwire with the new created setup on the new host. Don't forget to copy your templates.

    2) Manual by exporting the database and import it again.

    Copy your local files to the Webserver. Don't forget, that some folders need write permissions for Processwire to work(/site/assets /site/config.php, ...). You should have a phpmyadmin installed on your local machine. Use it, to export the database. Then import the database on your server(again, you could use phpmyAdmin). Check, if the database connection is possible with the login details saved in the /site/config.php. You might also have to delete the session and cache files in the /site/assets directory.

    By reinstalling a fresh PW, you would have to create the fields and template and page stuff again. You can copy the templates but the content will be missing ;) .

    • Like 3
  14. Welcome Peter

    I will try to answer your questions:

    - I saw an interview where Ryan mentioned a PW site with 100k+ articles. MODX Evo had a 5k article limit, which I was frustrated with. Is 100k the largest PW site out there? Are there any stats on PW maximum article limitations? Could it handle a million pages? (for example).

     

    First: There is no limit build-in into PW. It is using index-based DB Queries and a Ryan really had an eye for large-scaled sites. I've not that much experience with those large pages, but in my last project I've used arround 4000 single pages combined to a schedule and everything just worked fine. 

    There was a thread here in the forums, discussing a site with a million pages. It should be possible with some small modifcations. To gain more performance, you could use ProCache or other modules to speed up the site.

    Another larger example from Ryan would be the Tripsite .

     

    - One of the websites I need to build is not a typical website. It will be mostly private, with members each having individual logins (belonging to groups, as well). It will essentially be a large series of calculated data entry forms that will create a series of one-to-many data records in multiple custom tables, with a combination of text and numeric data.

     

    The user-role-permission system buildin should be able to do this. Have a look at the user and permission section on the API Cheat Sheet

     

    The calcutions part should be similar to Luis Web Application Intranet Case Study .

     

    I was originally going to build it from scratch, in PHP, but am now wondering if PW might be able to handle it

    From this brief description, could PW handle a completely customized interface and application like this?

    Yes. As Ryan describes it: Processwire is a CMF or a framework for mostly CRUD Operations in PHP shipped with an adminbackend for a Content Management System (/processwire). But maybe other people here could provide a more detailed answer.
  15. Same question here. I've got a site were special users should only edit a selected site (with all children in it). I want them to be able to create new pages aswell in their branch.

    I followed your steps and modified the Module. So far it works. But when I want to create a new page, I can't select the template for the new page.

    http://d.pr/i/e5QA

    The user/role has the right to modify the template. I cannot use a per-template approach because multiple pages with the same template (like "basic-page") should be editable by different users.

  16. I'm using MySQL Dumper  to backup the database. Configure it once and then you will have your backups as tar.gz files on the server. Now you could use Cobian to save these or - another feature of the MySQL Dumper save the backup to an external FTP server.

    It's running for two years now on my old forum without problems.

    • Like 3
  17. First impression is nice so far. I'm not sure how, but the Editor displays everything in German (that's good!). The feeling while typing is good.

    Only thing I'm missing: How can I prohibit the editor from stripping <i> HTML? Searched the config.js but didn't find anything.

    • Like 1
  18. Thanks.

    You didn't mention anything about the Email Image Module and letting party people / guests / visitors make pictures with their mobile phone and send directly to the website.

     That's a great idea. Would be a real good use case for the module. We just need to think about, who can post and when? Where to display those images. But I will keep it in my mind. Thank your for that.

     

    Something I've used in the past is a Java upload/download script, so if the promoters had a laptop (won't work on a smartphone) images would get appropriately resized on their machine on the fly before upload (search javapowupload) and really cut down on upload times (thus is how Facebook used to do it). It would require a custom upload form but can be done relatively easily if you wanted to go down that route.

    Yes, that would be probably the best solution. But I'm not sure if I could build such a inputfield. Our solution was just to explain the client, that their photographers should resize the images before sending them. They run them all through a photoshop/lightroom batch so it isn't a problem to shrink the images.
  19. http://urbanmotionbeats.info

    About the site

    Urbanmotionbeats is a party website featuring facts about events, galleries and a list of DJs. The main goal was to create a site, where they can upload their photos after a party. Processwire was perfect for this: We could make a template with all details about an event, add the image field and were ready to go. 

    Features

    • Processwire with ProCache enabled together with Lazyloaded images for a good page speed
    • Event template with gallery and several text fields 
    • Homepage with random images, latest events and some text.
    • Integration of the Facebook Comments and like boxes
    • Responsive/Adaptive Design, because a lot of people will using this from their smartphone

    Problems

    We mostly had client problems. How to use the admin backend. Where are the limits of the Backend? How can I do X? Why does Safari on Windows not work with Drag'n'Drop? I've never though about, what would happen if someone uploads 300 pictures from a DSLR with 20MB each (Script Timeout). We've fixed most problems but also learned alot. Overall you can say, Processwire performed well. If our not so tech-savy clients would have to use another more bloated Backend they would be totally helpless.

    What's next?

    This site is only the first in a row. Other event "brands" from them will follow with a slightly modified design. We've written a JSON output so we can later combine all events from all sites (4 are planned) together in a portfolio site with a more business focused audience.

    • Like 7
×
×
  • Create New...