Jump to content

Stefanowitsch

Members
  • Posts

    87
  • Joined

  • Last visited

  • Days Won

    1

Stefanowitsch last won the day on February 12 2019

Stefanowitsch had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Stefanowitsch's Achievements

Full Member

Full Member (4/6)

25

Reputation

  1. Yes you could do the yes/no questionnaire with two radio buttons. In my case I just want a simple fallback value for a non-checked checkbox to be visible inside the e-mail body. This is no problem with the API, my only issue is that the checkbox always will be set to "checked" after submitting - when there are validation errors inside the form. I find this to be solved much easer in "classic" PHP style and I will stick to that instead of the API form solution.
  2. Hi Robin! Thanks but that solution won't work for my case. Let me explain: For my forms I am using a "custom formbuilder" solution made from repeater fields. In the backend I can build my own forms with different elements in any order. After the submit I am iterating through the input values like this and build my email body content from that. foreach($input->post as $field => $val) { // get the $val and use it in e-mail body } Your code example does not work for me, because I am going through the fields one after one and the unchecked box will just be missing in the array. In case of unchecked I want to submit a value with "No" instead of nothing. $greeting = $form->getChildByName('greeting')->value;
  3. I am stuck with a problem: How to handle unchecked checkboxes via api. I have a form with a single checkbox. The value of the checked box would be "yes". When the form is submitted I want the value of the checkbox to be displayed within an email, together with a label text. That works. But we all know that when you don't check the checkbox the value of the checkbox will be missing in the post data. So in that case you can use the "hidden field trick": Create a hidden field that contains the value "no" and name it exactly like the the checkbox. This works perfectly fine with the processwire API like this: // create a hidden input for checkbox $field = $modules->get("InputfieldHidden"); $field->attr('name',$item->form_name); $field->attr('value', 'No'); $field->skipLabel = 8; $form->append($field); // create a checkbox $field = $this->modules->get('InputfieldCheckbox'); $field->attr('name',$item->form_name); $field->attr('value', 'Yes'); $form->append($field); My problem is: When you submit the form and some required fields weren't filled out, the form gets validated and the error messages are shown according to the required fields. So far so good. But in that case the previously unchecked checkbox is suddenly "checked". The reason for this must be the fact that the hidden field is submitted which has the same name as the checkbox that is visible in the frontend. So I guess that the processwire form handler then checks the checkbox automatically. This is not a behaviour that occurs in "normal" PHP post data handling.
  4. Wow that does the trick. Thanks a lot. The skip label markup syntax looks a bit weird at first but now I see that it is a mighty tool. I assumed that you just could write skipLabel = true. So the markup returns a number that the code is then working with. This does the same: $field->skipLabel = 8;
  5. This question is maybe trivial but I found no solution. When generating a form with the processwire API I want to make use of some hidden fields. When generating these fields the corresponding label is always shown in the frontend. Which in my opinion makes no sense (it's a hidden field, though!). This is the code I am using. $field = $modules->get("InputfieldHidden"); $field->attr('name','Name'); $form->append($field); On my form page in the frontend I then see a label called "Name" but no input (which is fine). The only solution that comes to my mind is to hide the label of the hidden field via CSS but that is not a clean solution.
  6. I installed the german language pack long time ago and I want to update it to the new version. What is the correct way to update the language pack? I just can't find the field anymore to drop in the ZIP file with all the data in it so that it will override the existing translations with the new ones.
  7. The problem with the special characters appears both on my local development environment (MAMP PRO) and on live site. I use the default PHP settings on both, nothing special. But this is no dealbreaker for me, I am not displaying any tags on the page.
  8. The content type of the response header says charset=utf-8 However here's the caption the tags are generated from. When printing this caption the special characters are all displayed correctly. •WERBUNG• Da strahlt nicht nur der #Pulli, sondern auch noch unsere liebe Aggi😁💯 #Spaß auf der #Arbeit darf nicht fehlen, oder? #fashionstyle #redhead #redpullover #fun #wilster #wilstermarsch #blackweekend #prozenteaktion #Spaß becomes spa<?>
  9. Thanks! I updated to Version 1.4.3 and checked the code line. Unfortunately the special characters still don't show up correctly 😞 I refreshed the PW module cache and the cache for the module itself but that did not help. That's not a big deal right now because the client I am working for wants the hash tags to be removed again (for layout reasons) but I think that might be a problem for other users at some point.
  10. Yes, I am outputting the single tags like this: <? foreach($item->tags as $tag) { echo $tag . ' '; } ?> On Line 1048 of InstagramBasicDisplay.module I tried this, but the hashtag is then missing in the array: $tag = $this->wire('sanitizer')->entities1($tag, true); $item['tags'][] = strtolower($tag);
  11. I have a problem: I want to display the hashtags for each instagram post. This is no problem at all. But the encoding seems to be messed up. For example special characters like "ä ü ö ß" turn out as the notorious PHP <?> symbol. When displaying the caption instead (which contains the hashtags) all special characters are displayed correctly, though.
  12. Hello! I was curious what became of padloper 2 and now I found this thread and I am blown away. The quality of this new module seems to be outstanding. I am VERY looking forward to integrate it into my next project. The project will be around winter/spring and I am optimistic that the padloper 2 will be finalized by that time 🙂
  13. This module rocks! It comes just in time for a recent project I am working on. Is there a way to send you a kind of donation for your work?
  14. Thanks for your reply! I was finally able to get it to work. In fact none of the cryptic steps mentioned here (https://developers.facebook.com/docs/instagram-basic-display-api/getting-started ) was necessary. I was in a rush and just copied this example code from the processwire module page to see what will render in the frontend. The problem was the line where a specific profile "username" was selected (as an example). I did not have an account like that in my module settings and that was the error.
  15. I just installed this module and am trying to authorize the user. Has anybody checked if the process of authorization which is described on the module page has changed? Basically I am stuck a the point where I need to generate a token and place it into the module settings. I have successfully generated a token, entered it but in the processwire logs I still get the message "username is not an authorized user.". Weird: After reloading the settings page in my facebook app the token which was just created seems to be gone. I found this instruction and the process of authorizing a user seems to be super complicated now: https://developers.facebook.com/docs/instagram-basic-display-api/getting-started
×
×
  • Create New...