Jump to content

csaggo.com

Members
  • Posts

    53
  • Joined

  • Last visited

Everything posted by csaggo.com

  1. @kongondo 1. yes, i just install blank profile for start usually (not sure about newest dev, if there are any profiles anymore, but it doesnt matter just a minimal pw-install with no language support) 2. in module core-modules just install/activate "Languages Support" 3. in setup-menu in addition to fields, templates and so on you now have languages with only one language (default) which is english 4. in setup for default language on the bottom there is a file field to upload core-translation files (there is also a link to the available language packs). Just upload the zip file for Deutsch right here, your backend is now translated to german. optional 5: in order to be able to navigate as you are used to you can add another language (english) just add english and dont upload a translation pack there. so it will be english as in default. You can switch in your user profile.
  2. @kongondoits been a while sorry. so i just added language english and switched my user profile to it. and .... it works with english. so it is in fact a multilanguage issue. to reproduce -> activate language support. Have only default-language in place and import the translation files: https://processwire.com/modules/german/ EDIT: Additional info. Once i had a property on the product, set my profile to german again, edited the same product, the search works fine for the existing property. But when adding another one, it does not work on the new one. So very specifically, it does not work on newly added property-line when the language is not english.
  3. hi @Jan Fromm thanks for sharing. so the obvious difference is that i have pw 3.0.201 will try with older version.
  4. @kongondo More debugging: i changed the core InputFieldPageAutocomplete.js - init Method like this: init: function (id, url, labelField, searchField, operator) { var $value = $("#" + id); var $ol = $("#" + id + "_items"); var $input = $("#" + id + "_input"); alert("changing"); console.log(document.getElementById(id + "_input")); var newId = "testCsam" + Date.now(); $input.attr("id", newId); console.log(document.getElementById(newId)); return; When i open the product page i get the alert "changing" two times (once for Brand and once for Type in Classifcation tab) When i then add a line in Properties tab I also get the alert two times as expected (once for Property and once for Dimension) See the console output in the screenshot: for the classification fields everything works, the id is changed to my test id afterwards and the element is found. if i inspect the element i also see my test-id for the two properties-fields you first see that the console-log output allready looks different. and most importantly the element with the test-id is not found. It is also not changed when i inspect it. i dont know enough about htmx and its afterSwap but whatever is done in the triggered init-method is obviously not applied to the final dom-elemnt(s) (including eventlisteners) and does not work.
  5. @kongondo it is in fact a JS issue: when i klick the little x on the right in order to clear the field, also nothing happens. It looks to me as if there simple all event-listeners missing for the input. EDIT: also the trash icon on the very right (to remove the whole property line) does not react on click.
  6. /processwire/page/search/for?template=padloper-dimension&limit=50&status<8192&get=title this is the link, the autocomplete has in his attribute to search. if i past this manually i find my properties. so they are definitly published and would show up if only the search would start.
  7. They are activated in the sense of beeing published. Can i see somewhere in the database if activated by Padloper? But i dont think thats the issue. As mentioned i monitored Networking in Debug Tools when typing in and there is no Ajax Request happening so it does not even try to find something.
  8. Hi @kongondo sorry for delay was on vacation. i have just retried with padloper 002 but still no search happening when i type. Language Support is installed but only default language exists (we have imported german translations) PW is latest DEV (3.0.201)
  9. Yes exactly for 1-3 4. i am not entirely sure but i think it actually did work at some point when i was playing around with it after first installing it. cant tell 100% to be honest. I also tried again with product settings to variants -> YES and even tho the markup js gets loaded, still nothing happens when i type the Property Name
  10. @kongondo hi, in this case i dont need product variants. Properties should be available anyways right? For variants i need attributes correct? so 1. no i am not able to add properties to the product. 2. when i click add new property the form appears like in first screenshot 3. exactly 4. did not try with variants, only have products without so far. i tried with variant article now and you are correct the js gets loaded in this case. but i think it always should be as properties should be allowed regardless of variants.
  11. allright i can confirm that the file is changed. but it doesnt get loaded on that product detail / properties page (see screen)
  12. Thank you, my downloadlink still gives me the version of june 3rd tho. Can you check again please. Thanks again!
  13. @kongondo sorry to bother with another bug report. On product-details i can not add properties in latest version. The search just wont start (i also see no activity in networks-tab in case it is ajax, the console also does not contain any js-errors) The properties and dimensions are created and published.
  14. @kongondo allright i have send a pm with temporary user
  15. @kongondo i have EUR (Austria) and for currency i tried both DE_DE and DE_AT (for Austria) i tried latest chrome and latest firefox on macos i would assume the root-issue is still that the value-attribute on the input field is rendered with comma as mentioned in first post, this would allready have solved the editing issue, the currency display settings for me are an additional feature. but i would take care of that where necessary in the frontend anyway.
  16. @kongondothank you for the new version unfortunately it does not work correctly for me - in product list it randomnly changes between showing a dot or a comma. see the two screens of list. - in edit it still loads attribute value with a comma and now displays the price but only without decimals (see third screen)
  17. @kongondosorry to bother, but do you have an ETA on this. Its pretty crucial for us, as we can't let our customer start editing product-data as long this is not working, they will just delete prices left and right. so our project is currently waiting for this fix.
  18. @alexmoh yeah i thought you suggested making it part of padloper itself, but custom field on the template makes more sense as there will be all kinds of different cases/needs.
  19. Hi @kongondo as allready briefly discussed in our email-exchange: We have PW running in german which means that in float - number fields the decimal point will be displayed as a comma (in fields as well as output rendering). The price gets stored correctly but when editing the product again, the price is not displayed and if you don't reenter it, it will be lost on save. In First Screen you can see that PW Float Field handles this correctly (displaying comma as decimal point but still using the dot in value attribute) In padloper price-field it uses the comma in the value attribute which the browser can't handle. so the solution should simply be to render the value with the raw version instead the output-rendering that includes the comma.
  20. +1 for this solution (shorthand field), we ran into the same issue with S, M, L, XL and so on
  21. EDIT: ryan allready fixed it, thanks ? Thanks for the hard work as always. There seems to be something broken in WireHttp in this version i filed issue report here: https://github.com/processwire/processwire-issues/issues/1506
  22. @ryan my i draw your attention to https://github.com/processwire/processwire-issues/issues/1447 thats quite a big deal for us "internationals" as it affects every place where the page Lister Module is used. i first thought it was in media manager but later noticed that its also in the page/lister/ and so on in the backend: bug: i cant switch pages. when i click on the arrow or page number 2 on the items list i get this error:{"error":false,"message":"Unknown Lister action"}
  23. @kongondoyes its a bug in the core since a couple of versions. https://github.com/processwire/processwire-issues/issues/1447
  24. thanks @kongondofor getting back so quickly. pw is 3.0.187 as mentioned, we use multilanguage indeed. we also use multisite (so basically we change the root-homepage with https://github.com/somatonic/Multisite/ based on domain-name) but my guess is, that its not relevant for backend. but you are right, the standard page-lister from the pages menü cant switch to page 2 either, so its a pw or setup issue... i will try to figure it out with ryan. also thank you for the doc-link i indeed missed that. perfekt ?
×
×
  • Create New...