Lenz

Members
  • Content count

    22
  • Joined

  • Last visited

Community Reputation

9 Neutral

About Lenz

  • Rank
    Jr. Member

Profile Information

  • Gender
    Not Telling
  • Location
    Germany

Recent Profile Visitors

313 profile views
  1. wow congrats on this hell of an achievement, also demonstrating the power of processwire as an app development framework.
  2. Thanks again @Robin S. I think i'll go with the Profield. As i understand, it should also be frontend editable via a modal. This way i have the best editing experience and at the same time i support the Development of Processwire. Thanks @all for your help.
  3. Thanks for your explanation, @Robin S makes sense. Ok, one question: If i have 150 items, should i better go with the Profield table or is a Repeater enough? I really like the nice unbloated editing view of the table field. Does it scale better? Is it also like a Repeater accessible for frontend editing (via modal)? Video of current fancy editor: Problem is, the editor is not working anymore, so unfortunately i could not show you a video. The editor called unify, but it's not developed anymore and the business around it is gone. It was essentially a ajax frontend without a database for managing content for static sites (directly write into the files). At this point i fear i made a mistake in describing the editing experience: If i remember correctly you actually also have a modal layer, as soon as you edit content - but it loads the page layout - so you edit wysiwyg. Dragging / sorting rows was indeed possible directly inline without a modal though. Similar editors are https://sitecake.com/ and http://www.coast-cms.de/ but i'd like to use Processwire edit: Thanks @Robin S for refering to my question regarding table field and frontend editing. Could perhpaps someone confirm that also the table field is frontend editable?
  4. @Robin S haven't try this yet. But you're right, many requirements would be met with your suggestion. Obviously i'm a bit unclear, indeed: So my wish is to edit directly inline wysiwyg without a modal layer, like you do e.g. with textareas. But meanwhile i learned, that's - at least per default - only possible with textfields or textarea fields, but not with repeaters, table, pagetable, image, file field types. For "complex" field types you have always a modal layer for frontend editing. And the modal layer displays the backend/admin ui edit-view of the field, not wysiwyg / not the page layout. So to achieve INLINE WYSIWYG frontend editing with CRUD + DRAG functionality, i have to invest quite a bit of hacking - without much knowledge of AJAX, which in turn would almost be necessary to not have page reloads all the time and to resemble the old edit experience... My customers are accustomed to edit / add / delete and drag data rows/ table rows directly inline wysiwyg and want to retain their edit-experience. But meanwhile, if i see e.g. the demo video of the Profield table field, the backend edit view is really very clear and unbloated. Repeaters are a bit more bloated and scale perhaps not so good as table fields. Perhaps i can convince my customers to go this route. And the table field should be accessible to frontend editing the same way as repeaters or pagetable fields do, i assume?
  5. wow @bernhard. Thanks. Thats a good start. As for Ajax. Yes, of course i'd like to do the actions without page reloading. Hm, could you point me to a good tut or resource? I haven't enough knowledge how to interact with PW if i want to implement actions the AJAX way...
  6. the item numbering is actually the dish position number: like Nr 71 | fried chicken | 7,90 like in these chinese cards edit: Maybe it's indeed better to do the numbering automatically, i agree. The customer said, that he wants to edit the number, but i don't remember at the moment, why...- i defiinitely will clarify this. It really seems to me, that pagetable is the option to go for me. Thanks for clarification. Regarding implementing at least add / delete items in inline editing: @bernhard could you point me to some good resources, where i could learn how to accomplish this? - Really thanks for your engagement !
  7. hi @bernhard, as for implementing an ajax request: Don't know how to accomplish that, never did this before...wait, no, recalling one incident implementing a registration form with ajax, it was a terrible experience... never got it really working, XAJAX comes to my rescue at that time ... Regarding the pagetable field for FE: But wouldn't a Repeater work for FE too, if i understand the posts above correctly? Or do you think a pagetable field is a better fit for a special reason?
  8. Thanks a lot @Robin S @tpr @bernhard for your valuable input. I have a few remaining questions Does this mean, that i can only edit Repeater items in inline mode and that i haven't CRUD functionality available in inline edit mode? Meaning, i can't add a new repeater, delete a repeater or drag a repeater to a new position? (see my example with the menu card, where every line/dish would be represented with a repeater ) @bernhard Actually nothing is bad about the Admin UI, if you ask me. It looks even good. But unfortunately my clients are accustomed to edit directly inline wysiwyg and don't want to give up this experience... @all: Let's say if i could convince my customers so they accept FE within Processwire as it is: Do you think that regarding my use case (see my first post) a repeater would do the job perfectly fine or has a Profield like "table" maybe advantages over a Repeater? Meaning, if i have 4 simple textfield wrapped in a Repeater vs wrapped in a Profield table field: Are these 2 scenarios essentially behave the same or are there differences? There are round about 100 - 150 entries in the menu card (inclusive beverage)
  9. Thanks @tpr for your answer. Good job! As i can see in your example: The frontend editing is only possible with a modal layer here? Or precisely could the modal layer display the edited page wysiwyg instead of their backend view? I mean with the build in frontend editor: Is it possible to edit repeaters or table fields directly inline without a modal layer or with a modal layer displaying the page wysiwyg? If so, would i also have CRUD functionality and drag&drop available?
  10. Hello all, i have a question regarding the following scenario: My customer wants to edit a menu card of a restaurant website directly in the frontend. Each dish / menu is displayed in a row with 4 simple textfields (position nmbr, name, quantity (optional, for drinks) , price). My customer preferably not only wishes to edit/update existing fields/rows, but also add a new one, delete one, or move an existing one up or down to a new position in the card. Would these actions be possible per default in the frontend edit mode, if i'd have e.g. a table profield storing the 4 textfields per dish? Or is this only functional in the backend? In a demo video of a Profield (-> fieldtype table) i saw the requested edit functionality (edit or add a row of fields, drag a row up/down, delete a row, safe) in the backend... Btw., regarding this concrete use case of a menu card: Would i have to use at all a Profield like table or could i accomplish the task also with a Repeater Field or a Pagetable fieldtype? In any case at least i don't want to let my customer mess around with a richtext field / inserting a table within CKEditor in the backend... Maybe there are better approaches than the above mentioned. Edit: I should add, that the site is a static one, equipped with an meanwhile dysfunctional inline frontend editor (that had the capabilitiy of editing, moving, deleting such rows directly inline in the frontend). Now i want to replace this editor with processwire. Thanks in advance
  11. @abdus thank you very much. That did the trick. I put the values (-> en_US.UTF8 ) without quotation marks in the translation field. Also i saw that there was already a string for the german language (-> de_DE), which i left untouched, but now i think it would be better to change it to de_DE.UTF-8 ... Anyway i strongly suggest to change the warning messsage to exactly the line you wrote me in your post, because that's clear and easy to grasp, imho. ok on hindsight - if one has a multilanguage installation - one should know what is meant by "please translate the C locale...", but still, i managed to misunderstand the original message whereas your line is 100% clear.
  12. Hello, i was upgrding to PW new master (3.0.61) from old master (3.0.42) and recieved the following warning (have a multilanguage installation -> german and english): Warning: your server locale is undefined and may cause issues. Please translate the “C” locale setting for each language to the proper locale in /wire/modules/LanguageSupport/LanguageSupport.module (shortcuts provided below): • English • German For example, the locale setting for US English might be: en_US.UTF-8* 1. Where exactly in the file LanguageSupport.module (which has some 900 loc) do i translate the C locale setting? - I couldn't find such a setting in this file... 2. Isn't it a bad idea to make changes to a core file, that normally should be overwritten by the next upgrade? Or do i miss something? Thanks in advance.
  13. very interesting discussion here. @LostKobrakai: If you don't mind, could you elaborate a bit more in detail why this new template strategy could be misunderstood or confused with a template engine? I really don't get the point, but would like to. To my - admittedly rudimentary - knowledge a template engine like twig adds only a little bit syntactic sugar like {{ var }} or something like {% block content %} Content of the page... {% endblock %} But what has this to do with the template strategy Ryan introduced here? And i also fail to understand in which regard the new template strategy could potentially lead to a tight coupling of markup with api stuff? I mean isn't the separation of business logic and view completely independent of using an engine like twig or not? Or in other words: Couldn't you mix up markup and business logic as easily with twig as wihtout it? Or again in other words couldn't you use the MVC pattern as easily with Ryans new template strategy as without it? (-> would like to know more about how to use MVC within PW templating btw...) just curious...
  14. meanwhile i have found out, that if i set the cloning permission directly at role level (Access -> Role -> editor) and disable the cloning permission on template access level, the page tree cloning works, but now the cloning functionality is assigned to all editable templates. I think for now i can llive with that, although i'd be happier if i would have been able to configure cloning per template...
  15. Hello all, i have a problem with page cloning, namely if i want to clone a page together with children pages (page-clone-tree) as a non superuser: Page cloning is a important requirement coming from the future editors of the website. reproduction of my problem: 1. login in processwire admin backend as user with the custom role editor 2. switch to Pages -> Tree View 3. click within the tree on the page which i want to clone 4. click on button copy next to the page (page has children) 5. result: ===================================================================================== page cloning doesn't work, instead reload of complete pages Tree and Message on top: "You are logged in". ===================================================================================== if a page has no children, the page cloning works. Also as superuser page cloning is functional. My system is processwire 3.0.12 multilingual the template of the parent of the page, which i want to clone has the following configuration for role editor: Tab ACCESS: VIEW PAGES ADD CHILDREN (makes no difference if i also add all other permissions like EDIT and CREATE PAGES, but the role editor shouldn't be allowed to create and edit pages on this level) Tab Family: May pages using this template have children ? -> YES Can this template be used for new pages? -> YES the template of the page, which i want to clone as editor has the following configuration for role editor: Tab Access: VIEW PAGES EDIT PAGES CREATE PAGES ADD CHILDREN Add permissions by role: editor: page-clone editor: page-clone-tree editor: page-delete Tab Family: May pages using this template have children ? -> YES Can this template be used for new pages? -> YES Allowed templates for children -> [child-template] the template of a child of the page, which i want to clone has the following configuration for role editor: Tab Access: VIEW PAGES EDIT PAGES CREATE PAGES Add permissions by role: editor: page-clone editor: page-clone-tree (doesn't make sense here, but makes no difference whether this is activated or not) editor: page-delete Tab Family: May pages using this template have children ? -> No Can this template be used for new pages? -> YES Have i overseen something or is there somewhere perhaps a bug? Thank you very much in advance.