Jump to content

Noel Boss

Members
  • Posts

    170
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by Noel Boss

  1. As I said, I have no control over that part… It works in my email client and is what gitlab provides for inbound issues… The one end I can change is my implementation of PW ?
  2. @Rich Torres You can create a new user like this: $u = new Page($templates->get('user'));
  3. To create a new gitlab issue, I'd like to send an Email to the following email address using FormBuilder: incoming+account/repository@incoming.gitlab.com unfortunately, the / in the email gets striped by the sanitizer: wire('sanitizer')->email(incoming+account/repository@incoming.gitlab.com'); // output: incoming+accountrepository@incoming.gitlab.com Is there any way to configure the sanitizer? Any other Ideas how to send the mail to this address? Ps.: I can not define the email format as it is defined by gitlab. The format is also kind of "common" and known as email-alias in the form of emailaccount+alias@domain.com – gmail uses it to label mails… https://help.wodify.com/hc/en-us/articles/234441508-How-Do-I-Create-an-Email-Alias-
  4. @tom. I totaly share our feelings torwards PW ? Just interested: Have you been using CraftCMS 3? What do you like better about PW than CraftCMS (3) Disclaimer: I have looked into Craft 2 before discovering PW but it ultimately liked in regard to flexibility of the backend and multi-langage or Multi-Site support imho… And the documentation of Craft is laking as well imho. And I was afraid to learn Yii2… But then again, NOT using a framework (PW) made me hesitant to use PW at first also. In contrast, I kind of like the "standard" approach oft Craft using twig and a mvc framework… And of course their design, gorgeous.
  5. I've also had this problem and opened an issue on github: https://github.com/processwire/processwire-issues/issues/672
  6. I'm not sure if this is related, but the search also does not display pages anymore for my searches… Also using Page Label Field extensively… Update: @ryan and @kongondo – I've found the culprit, it's when adding RuntimeMarkup fields to the page search fields: https://github.com/processwire/processwire-issues/issues/670
  7. It has not much to do with vue.js specifically and PageQueryBoss. You can make an AJAX request with any librrary, you build your JSON like the the link in medium above: https://gitlab.com/snippets/1729012 In vue.js, the JSON you get you add to the data of your component. I have not the time at the moment to explain in detail how we did it (apart from using Qusar as a starting point with vuex to store and retrieve data) but maybe this will help you: https://www.digitalocean.com/community/tutorials/how-to-use-vue-js-and-axios-to-display-data-from-an-api
  8. Please again consider this change. It would also allow you to add a dropdown for the children of the currently edited page (the one I suggested to remove ? ). You could add a slight delay for the hover – this way one gets not distracted. To add visual clarity to the behaviour one could turn the angle down – if preferred, one can keep the click target to these angles:
  9. Just released 0.2.4 of AdminThemeBoss with compatibility:
  10. Just my suggestion: Display the dropdown on hover over the elements … consistent behaviour like the top menu, then you don't even need the triangles anymore and also not the last item…
  11. Great module! I'm working on compatibility with AdminThemeBoss. I'd suggest adding the following css, because the default theme has a font-size on <a> inside the breadcrumb: .uk-breadcrumb >li { font-size: .875rem; } I personally would not even include the title because it's there twice with the page title… Also, I get an error when clicking on the arrow after the tree and then the root page:
  12. @bernhard I felt my post is not qualified for a tutorial with »step-by-step instructions on how to do things in ProcessWire« – and since the description for API & Templates contains »answers and support on the API and template development« I thought it would better fit in there. I was actually looking for a hooks / snippet / recipe section in the forum – but that does not exists. I know, there is https://processwire-recipes.com but it just feels to cumbersome to add one ?
  13. I truly would love to have the repeatermatrix interface for children, that would be amazing. If I understand you correct @tpr, i could use feel in the backend, but then I would have to build my own input-field or use RuntimeMarkup. Thats what I use currently, a page-table field with prefilled children:
  14. I use a PageTable field to make edits to children of pages more intuitive… To register the hooks, insert the following Snippet inside your init function in your module (or add it to your init.php file): /** * Initialize the module. * * ProcessWire calls this when the module is loaded. For 'autoload' modules, this will be called * when ProcessWire's API is ready. As a result, this is a good place to attach hooks. */ public function init() { // Prefill pageTable field $this->wire()->addHookBefore('InputfieldPageTable::render', $this, 'addChildrenToPageTableFieldsHook'); $this->wire()->addHookBefore('InputfieldPageTableAjax::checkAjax', $this, 'addChildrenToPageTableFieldsHook'); } Then, add this hook method: /** * Fill pagetable fields with children before editing…. * * @param HookEvent $event */ public function addChildrenToPageTableFieldsHook(HookEvent $event) { $field = $event->object; // on ajax, the first hook has no fieldname if (!$field->name) { return; } // get the edited backend page $editID = $this->wire('input')->get->int('id'); if (!$editID && $this->wire('process') instanceof WirePageEditor) { $editID = $this->wire('process')->getPage()->id; } $page = wire('pages')->get($editID); // disable output formating – without this, the ajax request will not populate the field $page->of(false); // you could also insert a check to only do this with sepcific field names… // $page->set($field->name, $page->children('template=DesiredTemplate')); // just specific templates $page->set($field->name, $page->children); } Now whenever there is a page-table field on your page, it gets populated with the children
  15. It's a fantastic module and I see its huge benefits for batch editing many children, when it's used in this context – But there are also some drawbacks for just using it as a intuitive interface to administrated some children: – Adding new items is a multi stepp process: Add, add title, save, edit – Backend interface is single language only (configurable using files that are not multi language) – Columns are not configurable. I don't want to display technical infos like Template and Name to the editor at this place
  16. I did note find a screenshot of Spotlight no the Mac, there it does not cover everything but just an extension below the search field – more or less exactly linke it is now, as a dropdown when you type the help command – as a first row of results. But before the actual results appear and you type anythin. Hmmm... Duckduckgo did not find anything, google does:
  17. Instead of a command, i'd simply include a ? Icon somewhere in the ui where you can click and get the infos… via tool-tip or toggeling a accodion section or any other form… Or, you could display the help info when clicking into the box right away, the same way spotlight does it:
  18. Your module does not work with my installation, am I correct that I need ProFields: Page Table installed? Using the Uikit Theme, but there is no markup for your Icons…
  19. I tried both but these also only go about 90% – I just again tried PageTable, is what's closest so far to what I would like.
  20. I would like to create new pages as children from your module – if i don't provide a parent when setting up the field, the create new link looks as follows: parent_id=0&amp;template_id=51&amp;modal=1 … it would be great if there would be an option to allow the current page ID to be passed to parent_id instead of 0 See:
  21. EDIT: What I'm actually really looking for is a way to edit and add children of a page in a similar way as RepeaterMatrix fields: Easy to add new ones and easy to move, hide and modify inline: –––– I have a problem and am so close to a solution, but everything i've found so far only gets me about 95% and before I create something on my own want to ask is anyone knows a soltion or if I miss something. My simple requirement: Editing Children and creating new ones inside the current parent page context – eighter inline or in a Lightbox. Not working Option A: With page relation fields I can create new pages – but it requires me to select a fixed parent. If I don't provide a parent, no new link is present. Not working Option B: With the awesome AdminPageFieldEditLinks Module I can create new Pages directly without the need to provide a parant beforehand – but then I need to select it at runtime. There is a new link now – the link is: parent_id=0&amp;template_id=51&amp;modal=1 … if it only provided the correct parent_id!!! But now i have to select the parent: Not working Option C : That's what I do right now… Reordering the Child-Field to the first tab – but to maintain the context, I would need the edit and new button to open a lightbox instead of a page reload. Possible solutions: For A+B: If I could provide a selector as parent, this would solve my issue: "parent=page.id" or a checkbox "use parent page for new pages". Or I could use some hook? For C : I could write my own javascript to open the links in a Lightbox.
  22. I have implemented this breadcrumb in my new theme:
  23. @matjazp The modules comes with all the source files required by the theme (less files etc) but what's actually included in the backend is only the uikit.variant.min.css file which is about 330k in size. It also needs some code to rewrite the css source file (the required method in AdminThemeUikit is not hookable) and a hook to extend the breadcrumb with edit links…
  24. Released 0.2.0 + 0.2.1 Theme is now a module extending AdminThemeUikit by replacing the CSS This simplifies the installation, simply download the module and install it Added extended breadcrumb with edit links Added option to activate the theme for all users Updated look of checkboxes and radios – thanks @flydev for inspiration Release 0.2.1; Styled login form
  25. It does not need to be updated all the time, there only need to be new ones once every now an then. A (bundled) theme with WP also only lasts for about a year or so. It's about a good starting point, nothing more. Since PW is pretty stable imo, a profile is totally okay. If you use Uikit at front-end and theme it, you could probably even update it quit easily. Have a elements implementet, maps, slider etc. with blog and comment > voila, ui-framework with themes on top and a few basic PW-templates as starting point for many people.
×
×
  • Create New...