• Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by mr-fan

  1. First could build a tree branch like: -questions_options --yes --no --don't care --could be changed...later and use a reapeaterfield for your you can "use" this kind of quiz on every page/template you need it... in the repeaterfield you setup your questions in the simplest mode with a textfield and a pagefield (using the question_options childpages...) to set the right answer - rendering on frontend is obvious with a simple foreach i think. tricky would be to save the entries from users....this would be more complex...;)
  2. Hi, yes you can work with simple repeaters for all questions of a form. For yes/no answers you can use a pagefield or fieldtypeoptions (pagefield would be more flexible if you need more features)... So you could render the form inputfields from the repeater field on frontend. You are on the right track. Best regards mr-fan
  3. the only userfriendly take that i know is going with the repeater matrix or pagetable route, in one project i drilled it with PageTableExtended with rendered Output on Admin Side and different "blocks" of content that a editor could add such as galleries, maps, text with image right or left....and full control over markup on frontend. WYSIWYG with full power is always a mess...on every system. If i've time to play i would try out a combination of repeater matrix for the storage in admin and some kind of "add block" layer on frontend with frontend edit for the single user works complete in frontend....this would be one step more userfriendly since everyone see instant like it is rendered in frontend...but that is just in my mind for now
  4. PW does alter/check every URL that is requested, you need to map it with url segment/url vars and make check if the urls that the script need are blocked. For using external scripts right you have to bootstrap processwire in your script so you can save and find the data via the API. For me i would go and setup the fields and templates in processwire and just simple use the calendar generation and you could use the HTML, JS and CSS and replace the PHP magic with PW API magic....this yould be much more flexible on the long run. regards mr-fan
  5. Just to clarify... a) you wanna integrate this tool into processwire? or b) you wanna use this script beside a processwire website?
  6. Thank you very much...very easy entry on this topic....the last years i used AdminCustomPages but this is a little bit outdated since 3.x so this will be the only way to go. Best regards from the neighborhood
  7. you can simple use things like $posts = $pages->find("template=blog-entry, categorySelect=$category, limit=10"); or your example with count() to be more efficient on big datasets...
  8. Like title says i've some domains with umlauts öäüß and i'd like to redirect them to the non umlaut version example: http://my-domä to i've somethings like this in my htacess: ##redirect umlautdomain (not my domain) RewriteCond %{HTTP_HOST} ^xn--mhldorf-nsb.d$ [NC] RewriteRule ^(.*)$$1 [R=301,L] in my config.php i only have in my hosts list... is there something that i've misunderstood? so far it doesn't work....but may the htaccess rules take some time to exicute...i tried since about an hour some different rules. regards mr-fan
  9. Just working on some smaller projects and take the step into the actual master/dev version and all the new methods and api chunks that are coming with the 3.x series... since i'm not always build websites i'm not always go with the brand new things and put them in my workflow....there is a 24 per day timelimit i think...;) BUT actual i dive deep in markup regions....and holy shit this feature ROCKS! It should put in place better than in some blogposts: or can some admins make a headline in the official docs and link to the blogentries?? This feature is to important to get missed for beginners and other users of PW! I'm just kick my whole workflow and change it for the markup regions....i'm feeling like xmas in summer Thank you @ryan Best regards and happy "new" year....
  10. Thank you for this great module and for fixing so fast...often when it come to the javascript debuging i'm a little lost...;) best regards mr-fan
  11. just tested with 3.0.65 and it seems that the pagelink field is not working? Best regards mr-fan
  12. Ok great that it works for you....a more complex solution with a hook on saveReady if SEO fields are empty put some own magic in there....if tey not empty do nothing... functions that i use: the hook itself works in admin.php under site/templates/: As always it is not the best PHP code since im no professional....but it works for me....if i somedays get some time i could add something like that with optionfields to the module itself. Best regards mr-fan
  13. Just fast from mobile.... You have to use a hook on pagesave and check the SEO fields there....I ve some functions for creating keywords and description from some given fields... May tomorow I can post an example...
  14. No PW plugin there...but some frontendstuff that could may be usefull: I doubt that there we be an opensource solution for such a complex ajax thingi that is mostly used in $hops there will be money to pay... Best regards mr-fan
  15. A addtitonal approach would be combination with AdminCustomFiles module. i use this to change the href of the view button where i've events that their single template creates an .ics file output and the editor only should visit/see the is my example. like in the module described a file called ProcessPageEdit.js under /templates/AdminCustomFiles/ folder: //used in a PW 2.7.x installation! //change the /events/ links in backend page edit for preview the events page not the .ics file! $(document).ready(function() { $("a#_ProcessPageEditView[href*=events]").addClass('found').attr("href", "/events/"); }); but the hook methode direct via PHP is the better way on more complex url creating....just mentioned my workaround
  16. No problem - like almost all things in processwire this could be set totaly free to your needs!
  17. Take a look: best regards mr-fan
  18. if you dive deepinto URL segments you will feel some "ProcessWires", too It's just to build the urls/structur that you need independently from your content storage in page tree...this is very scalable since you can optimize your pagetree (for editors, contenttype, datastructure) and the frontend presentation seperately.
  19. Well it is more a example of finding the right model to store things....if you would have 30 departments you would possible choose methode 2 or 3 for storing this kind of things...but the first model describes the most simpel way to store 1:1 connections - one member : one department.... Another thing that is here important this models are all show the usage of the pagetree in ProcessWire so a editor with a "small" company with "normal" amounth of departments could easy and fast manage his content....and we could fast get the data on frontend. On the Template side of life there you could read again on this from kongondo: These are just the basic examples for beginners - if you manage complex data and complex editing you could or better will use of ListerPro or even a own admin dashboard, hinding content from the pagetree that confuse the editors and make other strange but always possible things for managing complex content and at the same time give your users a good ui for editing this content. regards mr-fan
  20. Many new things are hidden in $urls for example is not in the API Reference....or just i did not find it. no problem for me since i like finding treasures and loot on the way - but just wanna mention it. Is there a chance to get involved or people could help extracting important bits from blogposts to the docs?
  21. you could use a template without a file...just as kind of datacontainer....and collect/view/edit this data in a other template/file like /doodle1/ shows all data from its childpages/entries... templates without files are not visible in the frontend, but you could use the API to get them where you wanna show them...;)
  22. like @LostKobrakai wrote are url segments for the whole store your weapon of choice... if you could live with and then /username/chart/....and so on you could all serve it from the /store/ template as routing to the needed data and users...
  23. Url can stay clean... ---doodles -----doodle1 (visible template that collects the entries for the doodle/poll ->url) --------entry1 (hidden page or no template - just a datacontainer with all fields you need) --------entry2 .... no changes everyone can reach a doddle via one link where you can show the existing entries and put a form for new ones... regards mr-fan
  24. ...a "members" module is a bunch of possible features that someone could imagine or thinking that this features are part of such a typ of module... so costs are really wide rage for the punchline "members module"... Pay a module is everytime needed when someone really could save time of development. I think if you've a basic feature list - there would be a price that someone is willing to pay and save time! I would for shure - for now using frontenduser module and some own scripts but i would prefer shared and supported module to own construstions on securtiy parts of a project... Edit: (or you talking only about the message system...? Such a system is only a own dashboard page with some scripting and two templates for the data under a hidden admin page...for this special case i think the more experienced devs are building their own system very fast) regards mr-fan