Fatal Error – Class Name Collisions

  • Resolved ollybach

    (@ollybach)


    6 years, 5 months ago

    Hi

    maybe i am wrong of course, but it looks like the plugin includes/requires the sofort libraries and classes all the time / everywhere instead of only where they are needed.
    If someone has installed 2 different shop systems (i.e woocommerce and another one)
    but both have a sofort checkout process and use/bundle the sofort libraries, you end up with fatal errors like class already declared or similar.

    Unless I am mistaken, and please correct me if I’m wrong – may i respectfully suggest to only require/include the sofort libs where and when they are needed please?
    (i.e just before the new Sofortueberweisung($configkey) and wherever else is appropriate instead of globally)

    thanks

    • This topic was modified 6 years, 5 months ago by ollybach.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author mlfactory

    (@mlfactory)

    6 years, 5 months ago

    Hello @ollybach
    i will check that.
    Cheers, Michael

    Plugin Author mlfactory

    (@mlfactory)

    6 years, 2 months ago

    Hello,

    in the next version the sofort lib are only loaded if needed (process_payment).

    The new version should be released end of this week.

    Cheers, Michael

    Plugin Author mlfactory

    (@mlfactory)

    6 years ago

    Hello,

    sorry this makes for me no sense because

    new Sofortueberweisung($configkey)

    is called only on process_payment() (WooCommerce Hook).

    So if you use 2 different Shop/Ecommerce Plugins – there should no problems – right?

    Cheers, Michael

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Fatal Error – Class Name Collisions’ is closed to new replies.