Jump to content

rugydp

Members
  • Posts

    11
  • Joined

  • Last visited

Profile Information

  • Location
    Switzerland
  • Activity
    Developer

rugydp's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hello Ikompagwec I just updated my test server to 1.6.0.11 and it looks like it is fixed. TinyMCE boxes are now disabled correctly on product pages. Regards, rugydp
  2. We have a shop running with four countries and each of the four countries has four languages activated, DE, FR, IT and EN. User friendly URLs are activated. We are running the site on an production server and on a testing server hosted at the same provider on different servers. It seems that on day X they switched to a LiteSpeed Web Server for performance improvement. Now the strange Problem: since day X we get a 404 message only on categories for two languages (DE & IT) in any country on both environments. All other user friendly URLs work in any country in any language. The hosting provider can't switch back and can't help either. We tried to regenerate .htaccess many times, reload the language, changing names of the categories and and and... nothing changes. We run the shop in "not user friendly" mode for the moment. Any ideas someone? Thanx a lot.
  3. When you are working on a multishop environment on "All Shops" all fields on the product admin page should be deactivated aka. disabled. For editing you have to tick the checkbox next to it to activate / enable it. That is a great feature, but it doesn't work on TinyMCE fields on our shop. What happens here: After the page product admin page is loaded all fields are disabled the TinyMCE editor appears and stays enabled. I am able to change the content of the description field and even press the 'save and stay' button. BUT: the content is not saved. This is really confusing for our users. When I click twice on the checkbox the TinyMCE textarea gets deactivated as it should be in the first place. Anybody else with this problem? I think it's a bug, but maybe only a problem on our installation? V1.6.0.9 Thanks
  4. Oha, klingt eigentlich logisch. Danke für den Hinweis. Werde das mit dem Kunden abklären... Schöne Woche
  5. Danke für Deine Antwort. Multishop haben wir für die vier Standorte in Europa. Unser Kunde liefert aber vom Firmensitz in Deutschland aus in mehrere EU-Staaten. Da sollte es doch möglich sein, in diesen Länder für die Endkunden den gleichen Verkaufspreis anzubieten. Ob Deutschland, Belgien oder Frankreich, das Produkt soll einfach überall z.B. mit € 30 inkl. Steuer im Shop erscheinen, unabhängig vom Steuersatz. Dafür für jedes Land einen Shop zu eröffnen (Multishop) erscheint mir hier etwas zuviel Aufwand.
  6. Hallo Leute Ich suche nach einer Lösung für einen Kunden, der Produkte in verschiedenen EU-Ländern verkaufen will. Der Verkaufspreis Brutto (inkl. MwSt.) soll z.B. für ein Produkt überall 30 € inkl. MwSt. betragen. Prestashop rechnet aber für jedes Land vom Nettopreis aus und addiert die MwSt. des jeweiligen Landes dazu. Das ergibt nun in Belgien (21%) einen Preis von 30.50 € und nur in Deutschland (Default Land - 19%) den gewünschten Preis von 30 €. Wie löst ihr das Problem und gibt es evtl. ein Modul, bei dem man den Bruttoverkaufspreis fixieren, bzw. als Berechnungsgrundlage definieren kann? Danke
  7. Okay, so your path is all right. It should actually change the order's state to 3. I'm afraid have no idea, why it shouldn't work. Sorry.
  8. Did you actually try to replace the $id_order variable with an existing ID of an order? You shouldn't need to include the classes as the line require_once(dirname(__FILE__).'/../../config/config.inc.php'); does the job. In modules context I hat to include it with ../../ to get it working. What exactly are you trying to do? Regards,
  9. Which code did you try? If you want to change a state of the order programatically, you need to create an order object with the id of the order and then set the current state with the order state id. These two lines should do the trick. $order = new Order($id_order); $order->setCurrentState($id_order_state);
  10. Thanks, vekia. Actually I'm developing a module to export orders as an xml file and change the state accordingly. I don't include or attach or redeclare the class in my module as I assume PrestaShop includes its core classes as needed. I instantiate Order objects without any problems, only when I call the $xxxx->setCurrentState() function it fails with mentioned error message. Do I miss some basic concept of PrestaShop development? Can't I use core classes for module development like using an API? UPDATE: I solved it. I had a line where I asked for an array of order states with a given state like: $orderIDs = OrderCore::getOrderIdsByStatus($this->ID_ORDER_STATE_PAYED); I changed it to: $orderIDs = Order::getOrderIdsByStatus($this->ID_ORDER_STATE_PAYED); and now it works. I really missed some kind of basic concept here. I still would appreciate some advise on when using SomeclassCore and when to use just Someclass. Any comments? Thanx anyways.
  11. I have the exact same Problem. Either I try: $history = new OrderHistory(); $history->id_order = (int)$id; $history->changeIdOrderState((int)$this->ID_ORDER_STATE_EXPORTED, $history->id_order); $history->addWithemail(); $history->save(); or $order = new Order($id); $order->setCurrentState($this->ID_ORDER_STATE_EXPORTED); I get the error: Cannot redeclare class OrderCore in [...]/classes/order/Order.php on line 2068 The error is triggered by $order->setCurrentState and by $history->changeIdOrderState. The object/instances are created without any problems. Only calling the functions/methods does not work. What am I doing wrong? Thanks
×
×
  • Create New...