Jump to content

arjen

Members
  • Posts

    1,222
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by arjen

  1. Thanks, the files were updated. It must have been cache. Although it seems strange since the version number bumped.
  2. Hi Teppo, Thanks for your efforts. Really appreciate it! I've updated the module but I'm still hitting the error. I uninstalled the modules and reinstalled them. The version number for VersionControlForTextFields is 1.0.3. When investigating I also found out that also a plain Text field keeps loading when switching history. If I enable TinyMCE both the plain Text field and the Textarea field are working. If I switch the Textarea field to a plain Textarea both fields fail. It seems TinyMCE still has to be enabled on one field in the template.
  3. An option would be to always show the icon. If a user clicks a field with no history a simple message like "There are no earlier versions of this field" would be sufficient. I will look into the version tonight and I will report back.
  4. Glad to help. I hardly ever feel the need to use a custom menu. If that's the case my Information Architecture is probably bad. I really like the idea of ProcessWire that your pages reflect your menu and thus your url structure.
  5. Codeschool seems to be rockin' these days. I even followed a Ruby course.
  6. I've ran into it again. You have to save the page twice once you have installed the module. In retrospect this is quite obvious, but if you install the module and you look for the icon it's not there at first. There has to be history to show the history. Teppo, is this module supposed to work with CKEditor? When I switch to another version it keeps loading. I'm getting a js error: Uncaught ReferenceError: tinyMCE is not defined. The field itself is configured as an CKeditor type. I'm running 2.3.0.
  7. I see what you mean. This would be my setup: 1. Create the normal structure (without the homepage children) 2. Add a checkbox fieldtype called "homechild" to your templates 3. Add the pages you want to appear under home directly under home and select the checkbox Your pagestructure would look like this: - Home -- Page 1 --- Page 1 child -- HomeChild1 -- HomeChild2 Use code like this: Checkout this gist. (edited the original post I made tomorrow to use gist instead - thanks soma) Written in the browser, but you should get the idea!
  8. I was thinking to use Piwik on a small project to find out how useful it is. This is a very nice addition!
  9. Great addition nik! Really useful module since I work a lot with Page fieldtypes!
  10. I experienced this too the first time. I uninstalled the module and set it up again. Don't really know what I did. Second and third site went smooth with the same setup.
  11. I'm not totally understanding what you mean. Can you share the code you already got? A screenshop of the pages list would be nice too.
  12. Thanks Teppo! Just installed it on a live site (after some testing) and it seems to work really sweet.
  13. Good to hear. Without Soma everyone is lost here
  14. Great tutorial! I think it might be helpful to explain why you use the wire() function instead of $page. I can image it might confuse your target group, being the new users.
  15. PW gets a notification on pineapple.io.
  16. Thanks Ryan for stepping in. For me the unpublished users are quite useful when using them for front-end purposes. When an (non-admin/non-backend) user registers I set them unpublished. This way they can't login. I'm working on a small module to set a user (un)published from the backend. I think this workflow is quite in line with the overal ProcessWire experience.
  17. Great addition Wanze! Might need this soon. Already started looking at the wat luis generated pdf's, but this seems great!
  18. Thanks nik! Really helpful as usual. The client loves it
  19. When I tried this locally it didn't seem work. I've done some other work, updated PW and deployed the website. Setting up some new stuff as well and now I can see the unpublished too. I must have done something wrong locally. I still want to extend this list so I might create a module to handle some useractions a little easier (set unpublished) if the client wants it.
  20. Soma, are you logged in as a superuser? When I look as a superuser I see them all, including guest and unpublished ones. When I look as the editor (with Administer user permission and the user template access) I only see the published ones (also guest is not showing up).
  21. That's what I thought. You recommend using a module? I think I can create one to display all the users and their status. If I run into any challenges I'll report back. Thanks Soma!
  22. Probably, soma Next challenge: the table is partially empty because only superusers can see unpublished pages (in this case users). Is there a way to show all users to non superusers?
  23. Didn't know that. ProcessWire keeps getting better. Thanks for your time, Wanze! I will try to figure out how to strike-through or dim an user who isn't published in the table.
  24. That works, thank you Wanze! Users with the 'editor' role can now see the users in the top menu using the Access page. Still can't move it in the tree view. Not much of a problem since they are accessible. Do you also know how to manipulate the table of users? The tree shows if a page (in this case a user) is hidden or unpublished. The table with users doensn't. This might be a nice UI touch to show an editor which users are published.
  25. I've setup a small member system. A new member can fill in a front-end form and is saved as an user who is not published. The editor of the site (no superuser) gets an e-mail that a new account has been made. Since I'm a superuser I can access the Users page in the treelist. It would be nice to show the Users page outside of the admin pages. I've tried to move them, changed permissions on the admin template, changed permissions on the user template. This is how I've setup the editor role to view the admin template. Is this possible? Or do I need to build a module? If so, any pointers to existing modules where I can mimic some features?
×
×
  • Create New...