Jump to content

nurkka

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

4 Neutral

About nurkka

  • Rank
    Jr. Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1,152 profile views
  1. Problem solved – Ryan pushed a fix: https://github.com/processwire/processwire/commit/f5f83e814880c862b5bfd0ee935b8c9e7699bd74
  2. Thank you both! In the meantime I have found the corresponding line of code in the FieldtypeOptions module. Before saving the options, ProcessWire checks, if the current user is a superuser. So any non superusers cannot save option values (in the current / newest ProcessWire version 3.0.148). So I modified the corresponding if statement, in order to allow users with "field-admin" permission. Thanks again for your suggestions. I took the opportunity to take a closer look at Tracy Debugger and I will definitely keep the page field select module in mind.
  3. Hi, I'm maintaining a multilanguage website where two different design companies have access to the processwire backend. For one of the teams I created a custom user role called "designadmin", where I activated the permissions "field-admin" and "template-admin", so the designers are able to edit fields and templates. This worked very well, but now, they wanted to create a select options field, and then change the values of the options. When clicking "Save" in the ProcessWire backend, the changed values won't save and are immediately restored to their previous values. Screenshot: When logging in as superuser, these values can be changed and saved successfully. How can I give the design team the permission to change and save options values, without giving them superuser access? Thank you for your help!
  4. Hi @kongondo, thank you for your feedback. I am glad that you like my suggestions. And I would be happy to help you with testing!
  5. Hi kongondo! Recently, I used Media Manager in a client project. In this real world use case, the media library very quickly grew to an extent, where it was too confusing for the client. Of course I know how to apply filters, but for my client, configuring and applying filters was to complicated - even with the relatively new feature of pre-defined filters. So I thought I would ask you, if you could image to implement some additional filter-features, that would make it easier for clients: - It would be great, if it was possible to set a default filter for every MediaManager-Field. I have a lot of different "image-types", like icons, fotos, sketches and so on. With such a feature, it would be possible to limit the displayed images to just the "type" of image, that suits the context of the current MediaManager-field. Like when applying some product icons, you don't want to choose from the whole library with all the staff portraits. - Another great feature would be, if pre-defined filters could be applied with one click in the overview. I tried to sketch this in a fake screenshot: In this way, an admin could pre-define all needed filters, and the user/client could just apply them with one click - without worrying about or even understanding the actual filter definition. I guess those features don't exist already, but if so, I would be very happy, if you could point me to any existing solution. Otherwise it would be great to have those - or similar - features in a future version. Thanks again for the great module!
  6. Thanks for the detailed explanation of the new module version! Some time ago, I wrote a simple module for a client website that converted every href-value on page render. It stripped out a certain folder name, i.e. it converted »/container-1/page-1/« to »/page-1/«. That worked fine, but for my client it caused a really big usability issue in the backend, because they saw the original links in the WYSIWYG-Editor, and not the resulting links. As much as I understand, the new Multisite version will also leave the original links in the WYSIWYG-Editors, like »/www.example.com/about/« instead of »/about/«. Do you see any way to just display the »right« links to backend users, while not really altering them?
  7. Thanks for your reply, Soma. And also thank you for developing the fantastic Multisite module! To further test this, I set up a clean installation of ProcessWire 3.0.30, activated link abstraction and put some internal links into the body-fields. Then I dragged and dropped the page branches around the page tree. PW’s link abstraction always correctly modified the links in the body-field. Then I installed Multisite, and link abstraction unfortunately stopped working. When trying to save a page with any link in the body-field, PW displayed an error message like »Session: Unable to resolve link on page "pagename" in field "body": /link-to-another-page/«. PW’s link abstraction internally saves page-ids as link-attributes in the database, like this: <p>This is an <a data-pwid=1023 href="/child-page-1/grandchild-page-2/">internal link</a>.</p> When Multisite converts links like »/www.example.com/child-page-1/« to »/child-page-1/«, PW isn't able to recognize them anymore and therefore cannot save the corresponding page-ids to the database. So I assume, link abstraction won't work together with Multisite. A powerful feature of Multisite is, that editor users see the »real« links in the backend. Modifying the links on page render, as you suggested in a previous post, would confuse those users, because they would see links like »/www.example.com/child-page-1/« in the WYSIWYG-Editors. The only solution I can think of right now, would be to convert all modified links back to the original links on page save, let link abstraction do it’s work, and modify them again, when displayed in the backend or frontend. Do you think that would be possible?
  8. The Multisite module (latest Version 0.0.6 from https://github.com/somatonic/Multisite/tree/dev) doesn't work correctly with the new link abstraction (since PW 3.0.6). When activated, the link abstraction feature adds the URL-parts of the Multisite-folders back to the URLs, so you'll end up with URLs like http://example.com/example.com/some-folder/some-page/ instead of http://example.com/some-folder/some-page/ I wrote a workaround, but unfortunately - since I didn't find a way to hook into the link abstraction - it's a core hack. I had to modify the methods sleepLinks() and wakeupLinks() in /wire/core/MarkupQA.php. In sleepLinks() I'm overriding the link modification, when a link points to a page, which doesn't belong to the current Multisite-branch. And in wakeupLinks() I'm stripping the Multisite-folder domain names from the given URLs. Since that doesn't make much sense in the long run, I wondered if anyone has a better solution? @ryan Ryan, could you perhaps make the link abstraction hookable? Or am I missing something? Every hint is very well appreciated. Thanks in advance!
  9. Hi, how is it possible to modify the settings of the html purifier instance that is used by InputfieldCKEditor? How can I get the correct instance $purifier? $purifier->set('Attr.AllowedFrameTargets', array('_blank','_top')); My goal is to allow link target "_top" *without* having to disable html purifier ...
  10. Thanks LostKobrakai, this is the trick I was missing.
  11. Hi Peter, yes that would work, though it's not very easy for the clients. I thought I missed a trick with dragging/dropping pages, but it looks like the pagetree simply lacks this feature. What would be the best way to post this as a feature request - in github issues or here in the forums?
  12. Hi, when moving a page in the page tree via drag'n'drop, it was not possible (for me) to move it one level down beneath another page. This only works, when the destination page already has a child page. Is there a trick to do drag and drop a page one level beneath another page, even if this page hasn't already got a child page? I tried this in Firefox and Chrome. Thanks in advance.
  13. Thanks for the module, Macrura. Currently I have page fields and option fields with InputAsmSelect on my pages. Now, with the module, the options are editable too, which leads to strange results. Is it possible to restrict the module to only modify page fields? I tried $field->type within InputfieldAsmSelect::render, but got no value back.
  14. As far as I know, there is no built-in way to do this. You would have to use a module or write one yourself. I found this post from ryan to be very helpful on that topic: https://processwire.com/talk/topic/1799-routes-and-rewriting-urls/#entry16754 In this thread you'll also find further information about rewriting urls. If you're rewriting urls there will certainly be side effects like the link module in ckeditor will not work properly anymore.
×
×
  • Create New...