Jump to content

csaggo.com

Members
  • Posts

    61
  • Joined

  • Last visited

Posts posted by csaggo.com

  1. Hi @kongondo

    long time since we spoke, i am in the process of going live with another padloper shop as the first we started is still on hold on customer side...

    i just developed a custom payment module for klarna hostet payment pages.

    two things did not work as expected:
     

    in the __construct method i had to put 
     

    (array $klarnaConfigs = null)

    instead of just 

    array $klarnaConfigs

    as parameters, because when it instatiates the module the first time on padloper - addons page, it wont be able to, as it does not pass configs there.


    the second issue is more important:
    in PadloperUtilites the methods getNonCorePaymentProvidersIDs, getNonCorePaymentProvidersNames, getNonPaymentCustomAddonsIDs, getNonPaymentCustomAddonsNames will not work if i am not logged in as a superuser (so being able to access all pages). I had to add check_access=0 to the processwire-selectors there.

    this should be fixed for future updates.

  2. @ryani like tinymce alot. What i'm coming across that some stuff is not inline-css but classes like "align_center" now that works in the editor but my uikit-frontend does not know about this.
    I didn't figure out how to set it up that the align center entry uses uk-text-center instead or additionally? or do i have to remove the original align menu in the settings and set it up as my own "uikit-align"

    or is there a frontend css file i can simply add to frontend?

  3. on php 8.2 i have the same errors:
    for a temporary fix until it is updated i just added these lines to Padloper.module:

     

    public $padloperDownloads;
    public $outOfStock; // added for 8.2
    public $productNotFound; // added for 8.2
    public $checkYourOptions; // added for 8.2
    public $session_id; // added for 8.2

     

    • Like 1
  4. On 10/21/2022 at 3:47 PM, kongondo said:

    Do I?

    1. Install ProcessWire and select a non-language profile.
    2. Activate language support (not sure how to do this - never done it before; are there instructions somewhere? thanks)
    3. Default-language in place: is this English?
    4. Import translation files: Never done this before. A hint or guide would be helpful, thanks...

    @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.

    • Like 1
  5. @kongondoits been a while sorry.

     

    Quote

    the other tester's sites are not multilingual or at least currently have English as the default language. Might not be related, but worth mentioning.


    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.

    • Like 1
  6. @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:

    821760530_Bildschirmfoto2022-07-06um21_53_48.thumb.png.3aebbd6f5ae37d36cdab5cc47b95b972.png

    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.

  7. On 6/9/2022 at 11:25 PM, kongondo said:

    @csaggo.com

    I am wondering whether the dimension and property pages you created are not activated (by Padloper). 

    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. 17 minutes ago, kongondo said:

     

    Again (sorry) to be crystal clear, your issue is:

    1. You click on 'add new property'.
    2. A new blank row for properties is added to the DOM.
    3. You try to search for a property (e.g. Breite) or a dimension (e.g. Milli) BUT NOTHING happens.

    Am I correct about 1 - 3 above? 

    4. Secondly, has this worked previously then it stopped working? 

    Thanks.

     

    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

  9. @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.

  10. 18 hours ago, kongondo said:

    I always check before I make an announcement but I have checked again and it contains the correct files ?. There is only one changed file (InputfieldPadloperRuntimeMarkup.js) as the issue was caused by JavaScript. I am wondering if you browser is still serving previously cached values? Please let me know, thanks.

    allright i can confirm that the file is changed.

    but it doesnt get loaded on that product detail / properties page (see screen)

    Bildschirmfoto 2022-06-09 um 11.27.56.png

  11. @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. 
     

×
×
  • Create New...