-
Posts
6,671 -
Joined
-
Last visited
-
Days Won
366
Everything posted by bernhard
-
-
one thing i'm missing sometimes on the template editor is a shortcut for editing field widths. a slider from 10 - 100% instantly changing the fields width would be a great addition in my opinion often changing one field's width makes it necessary to change the other field's width as well (eg adding a field to a row of 4 fields with 25% makes it necessary to change all fields to 20% it would be great to add the field and drag all field's width from 25 to 20 without the need to open each fields settings, clicking on the display tab, changing value, saving field, closing modal... all other settings are fine being available behind one click.
-
i don't understand what you mean jürgen... you can edit the field's position in the template editor. it's only 1 click away from the page-edit-screen.
-
depending on the amount of entries frontend filtering could also be an option: http://ohmspeaker.com/speaker-filter/?length=13&width=10
-
h1 is float: left; - i don't know why, it must have to be a setting of AOS. it's quite hard to find out what setting it could be so i thought you may have an idea?
-
hi tpr, do you know where this glitch comes from? how it should be (AOS off): how it is (simple process module just returning "hallo"). sticky header OFF: is this a bug or did i forget a setting? thank you for your help!
-
yeah, i know you can do all kinds of stuff in the admin. still i think it would be good to have a checkbox for that. there have been lots of people requesting such kind of field-groupings over the time and i think it would be better to solve that by providing a checkbox than letting people solve the problem all on their own and having no standard way of doing it (you can remove it by php, by css and also by js...). second best option would be to have it in AOS. maybe i find the time to file a PR next year for that...
-
jep, there are data attributes <li class="Inputfield InputfieldRepeater Inputfield_address InputfieldItemList InputfieldRepeaterMax InputfieldRepeaterMin InputfieldColumnWidthFirst" id="wrap_Inputfield_address" data-page="1001" data-max="1" data-min="1" data-depth="0">[...]</li> would there be any drawbacks removing the label by default if it is min=1 and max=1 ? here's the field compared to the original: original:
-
Wishlist: Group field for grouping fields
bernhard replied to steveooo's topic in Wishlist & Roadmap
your post kinda proves that it is a good idea to hide the label. because in my example it is already hidden that's the original setup: the whole dark line is unnecessary and counterproductive! -
you can now use repeaters for that! @tpr maybe hiding the label when using it with limit 1/1 would be an option for AOS?
-
hi ryan, nice updates as always! what do you think of adding the option to hide the label of the repeater item. that way you can use repeaters to setup reusable groups of fields. or do you see any drawbacks with this technique?
-
Wishlist: Group field for grouping fields
bernhard replied to steveooo's topic in Wishlist & Roadmap
just tried the new repeater updates and it seems like a perfect match for this request! almost. you would just have to hide the label of the repeateritem then it looks really nice! keep in mind that selectors could get more complex when using this approach! -
do you have some user input or are you creating the pdf completely on the server side (like cronjob)? if you have some user input you could create an image of the chart first (eg on button click) and then post this image to your php script and integrate it in your pdf
-
hi timothy and welcome to the forum, maybe it would be easier to use a client-side javascript library to create your pdf? https://github.com/MrRio/jsPDF
-
hi lostkobrakai, i think you didn't get me... see this screencast. i think it is much nicer to hide the select via css (after the reload) than having it show up and hide it afterwards: anyhow... if you do not like this enhancement i'll just leave my line css in place. but i don't see a reason not to add this by default for every chosen input field #Inputfield_my_chosen_select { display: none; }
-
thank you lostkobrakai, awesom module! suggestion: could you add a css rule that hides the select input right from the beginning? it is hidden afterwards via jquery anyhow but as long as it is visible it leads to some ugly display of the unstyled select field. do you understand what i mean?
-
How do we enable html tags in fields setup "description" box?
bernhard replied to Zahari M.'s topic in Getting Started
just for the record, it is possible to add html to description via hook without messing around with str_replace or the like: $this->addHookBefore('InputfieldPage::render', function($event) { $field = $event->object; if(!in_array($field->name, array( 'fieldname1', 'fieldname2' ))) return; $field->entityEncodeText = false; $field->description .= ' <a href="#">test</a>'; } -
thanks, i've seen this video before but it does not seem that anything happened since pw 2.4?
-
maybe if you look into this in detail i think it would also be nice addition to be able to paste images directly from the clipboard. this is a nice timesaver when uploading screenshots (for support or the like). but it's not a necessity... whereas i think client side image resizing is
-
@since 1.1.5 added CTA Button to ProcessDatabaseBackups page (edit backups) 2016/11/28 for anyone wondering as well
-
i guess a blog-post with a good tutorial about how to create the most simple rest api and then, in the next steps, adding things like error handling and authentication and so on could help a lot for bringing in light to this topic there's already the great tutorial of @gebeer , but i guess that's not what looks "incredibly simple" to the eyes of someone who does not have a dev background...
-
the sad thing is i do not expect to get an answer here as i put some time im my last post and did not get an answer either... anyway, from the roadmap 2016: what about the client side image resizing? that would be REALLY helpful in many of my projects... i'm still voting for a rock-solid image handling field. like cropping in predefined ratios and so on. that's an often discussed topic and i don't think that horst's awesome cropping module is the best solution... in my opinion it still feels like a workaround and not like processwire awesomeness... but of course many many thanks for all the great work that lets me have so much fun in my everyday work
- 17 replies
-
- 10
-
-
ah ok thank you for clarifying, it's hard to follow all messages exactly in this thread
-
I think tpr already fixed the menu on default theme and created an issue on github? On mobile, I can't link to it...
-
@adrian yes, exactly, totally missed that! @tpr now that you mention it i guess we already talked about it... not sure if you understand me right as a new admin theme would be a totally different beast. but not so important anyhow