bernhard

there was some discussion about this years ago: don't know how ryan sees this nowadays where pw should be more a framework than a cms...

same here

jep, i think you are right with this

related to the helpdesk topic i want to suggest that you offer the possibility to support this awesome project (module seems like an offense in that case) with donations and mention the donors somewhere in return. what do you think of that? I'm really thankful for what you built here as i learned a lot and i don't know where i would be today without all the help of tracy opening my eyes. maybe it's just me because tracy came in right in time and i've never used xdebug or the like - but i have the feeling i'm not the only one thinking a bit about it i'm asking myself if that wouldn't be a good feature for the modules directory? offering a donation button connected to the devs paypal account and showing the donors automatically ranked by amount? if that is getting too offtopic don't mind creating a new topic for it... my first intention was related to tracy though, so i'll leave my comment here

ok throwing in some more ideas here as i think it would really be great to have something like this. i think the priority should be to help US at our work with our clients and not to develop something that spreads the word about processwire... imho the most important parts would be feedbackform directly on the page where the issue occurs (i always have to teach my clients that they send me the URL with every request they are sending). like in my post in tracy (see below) copy&paste screenshots would be awesome: https://github.com/vladmalik/pasteimage simple overview system both for clients and for devs simple notification system i'm really short on time but would help as much as i can if something like this would arise. i'm also willing to sponsor some euros for such a project

creating something cool is the one thing, keeping it up to date is the other... that's the more challenging part. you would have to make sure that all installations of your system can get updated if the user decides to. that's a pain with site profiles. so i agree it would be cool to have simple project/task/ticket management in pw but i think the only possible way would be to develop a module. installable, updateable, maintainable... gitlab has recently announced their new issue board. that looks really nice from what i saw on the video: https://about.gitlab.com/2016/08/22/announcing-the-gitlab-issue-board/

i have no problems on one 2.8.28 installation. i always use shortcut methods like this (you have to check the "enable shortcut methods" checkbox for this // test tracy dump anywhere in your files bd('tracy dump working'); im not sure about this backslash... i get the same error on pw3 when using TD::... everything works when using shortcuts

the code is in your linked example, so what is your exact question?

found a little display glitch on collapsed fields (standard theme pw3):

thanks for clarifying!

haha ok sorry for that, i corrected my post here is the link: http://processwire.com/blog/posts/tesla-model-s/ @horst is it possible to share some details about that? what is planned? there was a lot of discussion around this topic in the past, i think it would be good to consider some of that feedback for a new version of the corefield (or will it again be a module?). i can't find the right topic now where we were talking about presets in the core field... what i found was only these two topics: and still on my wishlist, because that would make building image galleries a breeze: any chance that client side resizing finds its way to this update? at least it was mentioned in the roadmap for 2016 https://processwire.com/blog/posts/happy-new-year-heres-a-roadmap-for-processwire-in-2016/#what-else-is-coming-for-processwire-3.x-in-2016 thank you for all your work on the images field so far!!

In the last Blog Post Ryan said he and Horst are working on it have had a chat about it... On Mobile no Link sorry Link in the next post

thank you guys, especially @Soma, helped me a lot! i totally forgot i had to inject the variable on my own in frontend. when i was logged in it was present because i use frontendediting and there it gets injected automatically. totally makes sense i took a slightly different approach with my own js variable: // template <?php echo $modules->get('PwFullCalendar')->render(array( 'editable' => $page->editable(), )); ?> // module public function render($options = array()) { // get settings $settings = array_merge($this->settings, $options); extract($settings); // push settings to javascript $out = '<script>var fullcalsettings = ' . json_encode($settings) . ';</script>';

i need to share some variables between my backend and frontend. i tried using $config->js for that: https://processwire.com/api/ref/config/js/ the strange thing is that it throws an "Uncaught ReferenceError: ProcessWire is not defined" error - but only when i am not logged in! i tried it on a different install (both pw3) and there is the same problem. is that intended? what can be the problem? _main.php [...] $config->js('test', 'bla'); ?> <script> $(document).ready(function() { console.log(ProcessWire.config.test); }); </script> ok without the document.ready i get the error both logged in and logged out... even more strange any ideas?

ah ok thank you i didn't get that

works! may you add an issue on github?

@Kemal you are right, you have to add the api key to the google script! you can limit requests to the google api in your google console to your domain to prevent abuse from other people. @ukyo thanks for the fork, any news about an official pull request / merge?

hi @thetuningspoon just wanted to say thank you! i looked to your code and it was really easy to implement my own fieldlink (needed some special selections) like this: php hook: /* pagefield for league selection */ $this->addHookAfter('InputfieldPage::render', function($event) { $field = $event->object; $pages = $this->wire->pages; if($field->name != 'league') return; // load script $this->config->scripts->add($this->config->urls->Webifex . 'pagefieldReload.js'); $admin = $pages->get(2)->url.'page/'; $leagues = $pages->get(1017) // settings ->season // current season ->child('name=ligen'); ob_start(); ?> <div><a class="pw-modal" href="<?= $admin.'?open='.$leagues->id ?>"> <i class="fa fa-edit"></i> Ligen verwalten </a></div> <?php $html = ob_get_clean(); $event->return = preg_replace('/<\/div>$/', $html, $event->return); }); and this simple javascript: $(document).on('pw-modal-closed', 'a', function() { $(this).closest('.Inputfield').trigger('reload'); }); awesome

sorry for being unclear i'm talking of the menu dropdowns. they flicker when entering with the mouse from the bottom:

hi tpr, maybe if you find the time it would be awesome if you could fix/report/pull request the issue with the flickering dropdowns in admin as well as you just fixed that at buttons. maybe it's the same issue? although i think that should be considered to be a bug and should not be something you need steroids for... maybe you can make an issue on github and talk to ryan what is the reason for it? thank you

its located in processpageedit module i also found that by coincidence some day... http://kongondo.github.io/ProcessWireAPIGen/devns/source-class-ProcessWire.ProcessPageEdit.html#93-112

thank you robin! you got me on the right track - i had a field dependency on another field that was not shown. i have to show both fields then it works!

if have links like that: /admin/page/edit/?id=1398&fields=title that works great until the field is inside a fieldsettab. it does not show any fields how can i solve this? edit: got a little closer: you can link to the tab like this: ?id=123&fields=yourtabfieldname but it shows the whole tab. not only the field i need. any hints?

hey adrian, what do you think of a panel to switch off certain modules. like the panel selector but not for panels but modules. so you could switch off modules during development to make sure it is not related to that module... no idea how hard that would be - just wanted to share the idea and hear your thoughts

i open the pagetree in a modal like this <a href="/admin/page/edit/?id=123&modal=1" class="pw-modal" ... that works great for pageedits. but if i open the pagetree (/page/?open=123) the page opens in modal-mode, but if i click on edit, the &modal=1 gets lost and the whole admin page gets loaded in the modal. is there an easy way to stay in "modal-mode"? i want to get rid of all the breadcrumbs and menu stuff here: @Pete again... "please wait 40 seconds before submitting" thats REALLY annoying when i just want to edit my original post. any chance to deactivate this?