bernhard

i'm using a sandbox-page for some api testing in my root-folder with bootstrapped api. the file only contains: <?php include('index.php'); // quick way to test api i'm using 1.5.7 on pw 2.7.3

hi szabesz, of course i meant this panel to appear only for logged in users (clients). i guess it would be VERY good feeling for the client if she is working on the site and has a support or help badge on every site. something like a toggle on the right of every page. when clicking on the panel, there could be something like "ihr ansprechpartner" on this site: https://www.maletschek.at/boote/phobos-dalpol/phobos-21/ do you get what i mean? i think that would build trust and satisfaction for the client (not the website visitor). the most important thing of this panel should be a message box with a button "send comment" something like this: i meant a panel for admins/devs, where they can filter all submitted comments. an example: client comments: - comment 1, page A, url /page-a, template event - comment 2, page B, url /page-b, template guestbook - comment 3, page C, url /page-c, template event - comment 4, page A, url /page-a, template event when fixing comment 1, it would be nice to have a button "show all messages related to this page". also it would be good to see comment 3 as it is related to the same template. clients would of course not need to do anything, as processwire knows all this from the referred page i think such a feature would be great, but i'm not sure if tracydebugger would be the right place. maybe a dedicated support module would fit better? ps: i really like the idea of logging errors on the client side as stated in the link in my posting above. don't know how hard that would be, but think of a comment like "XY does not show up on this page" and you could inspect a log of the clients console like "undefined variable xy..."

jep, that is correct. ok i think a comment feature with notification via email would be great! i always have to educate my clients to post the url where they are referencing to into the support mail. often they forget it. when they are able to comment directly on that page and not even have to open their mailclient it would be very handy! maybe also put name + email + phone on that panel? like "how can i help you?" leave your question directly here on the page or write me a mail or give me a phone call for more complex questions: xyz@example.com, +123 456 789 maybe that would make screenshots unnecessary in 90% of the cases, you could be right here PS: maybe a support-panel, showing messages with kind of filter functionality: show messages related to: this page | this template | this website show messages depending on priority: high | medium | low show messages depending on type: bug | request | comment

ok, so here is my letter to santa claus https://usersnap.com/features/feedback-widget-bug-tracking but my clients are even too lazy to use greenshot for screenshots... so i don't know how much they would use such a tool... oh, and of course: enjoy your vacation!

see also this post and my javascript solution: https://processwire.com/talk/topic/11538-pagefield-–-limit-number-of-choices/?p=107504 (and also tpr's modification) should not be too hard to adapt the code. putting everything into a modules would also be nice... it was beyond my head then and now i'm really busy, sorry

On mobile, but isn't there a setting for that already built in at the field?

That is great! Thank you Adrian, very good idea!

sounds cool, but i don't have time to wait maybe i can try to work with it on my current project and help testing?

thank you lostkobrakai and tpr for your insights to nette forms! i will try that

oops, forgot the link thank you

thank you jürgen, http://formvalidation.io/ looks awesome! would have needed this some weeks before for some quite complex forms...

for reference: adrian's template setup batcher can save you time

hi am*, welcome to the forum. one thing to add may be that you REALLY have to invest time in planning your site structure. that's one of the most important parts when building sites with processwire. as everything is a page and every page has it's very own place to live! if you did your homework here, seemingly complex tasks can get surprisingly easy. like in this example (https://processwire.com/talk/topic/13183-adopt-field-values-as-defaults-from-parents/): blynx built a module to inherit field values from parent pages, whereas in your template file you could just do this: $foo = $page->closest("foo!=''")->foo so you have to organise everything in a strict hierarchical structure - the pw page tree. i would recommend you to do some test projects (https://processwire.com/docs/tutorials/hello-worlds/) and then share your planned site structure with the community. you will always find a helping hand here

but how is this code generated? and how the images? i find some scrollmagic words in the code of my linked website, but on the scrollmagic site the demos do not look like one can make such websites with it?! thanks for your answers so far

also very nice! i wonder how that is done? i mean... i understand normal css animations, but i have no clue how the glasses get devided into separate parts when scrolling?? does anyone have some sources to read for me?

i've shared a nice website once and there where some opinions that it was too heavily animated... though i want to share another one, as i have never seen such a great experience for a one-pager / scrolling / animation site: https://www.imaginecurve.com/ what do you think about it? ps: neither tested on mobile nor inspected loading or cross browser compatibility... on my chrome desktop it was just impressive

thank you adrian, that's great! i didn't think about dev-sites. that's surely a good thing to be able to check the markup before going online

hi wanze, would it be possible to change the markup a little bit? i got a message that my sorting module ( https://processwire.com/talk/topic/13064-inputfieldfile-image-sorting-autosorting/ ) does not work with your securefile fieldtype. the problem is, that my module sorts the files based on the selector: tinysort(field.find('li.InputfieldFileItem'), {selector:'a.InputfieldFileName', attr:'title', order:direction}); and you are modifying this markup here: https://github.com/wanze/FieldtypeSecureFile/blob/master/FieldtypeSecureFile.module#L98 one solution would be to create a different selector for your fieldtype... i failed when trying to find a solution. would it be possible to modify your markup to an anchor: <a class="InputfieldFileName" title="thefilename.ext">...</a> thanks

added the module to the modules directory and changed version number to 1.0.0 please let me know if anyone experiences problems

I'm doing it almost like szabesz explained, but using $config->opt = $pages->get(xyz); so i have it also available in included template files via wireRenderFile(xyz) then you can do $config->opt->yourfield everywhere

why?

Ryan solved this in pagetable as that pages created but not published are deleted automatically each day by a kind of lazycron. On mobile and no details for that... Just throwing in an idea

I don't think this would be easy unless using the menu builder module. I also don't think that it is a good idea to build your site structure like this. Have you thought of deviding your tree in one branch "menu" and one branch "helpers" or "options" or "data"? Maybe this would make things easier. You can than rewrite the URLs from example.com/menu/page1 to example.com/page1 I'm on mobile... Use Google and you will find how to do that

don't know what this RCDMap.js is, but i created a simple fiddle for you. does this help? http://jsfiddle.net/T78Hd/13/

You can append a variable to the CSS to prevent caching: your.CSS?v=160422