Jump to content

amaische

Members
  • Content count

    18
  • Joined

  • Last visited

Profile Information

Recent Profile Visitors

8,164 profile views
  1. amaische

    HoneyPot Captcha

    Yes, it seems as if the email is coming from my contact-us page.
  2. amaische

    HoneyPot Captcha

    Hello, I have installed Honey Pot Captch V 1.12 in phoenix 7.15. It works fine, but I still receive emails with urls in it (if I copy it to the online contact us, it is correctly rejected with an error): The log tracker shows the following: How is this possible ? best regards amaische
  3. Hallo, ab dem 01.07. gilt das OSS-Verfahren, bei dem über eine zentrale Meldung die Umsatzsteuer an das jeweilige EU-Land abgeführt werden muß (die bisherige Schwelle wurde für alle EU-Länder zusammen auf 10.000 Euro erniedrigt). Wenn ich es richtig verstanden habe, muß dann im Shop (bei Einkauf von Privatpersonen und Unternehmen ohne VAT-ID) die länderspezifische USt ausgewiesen werden, d.h. z.B. USt Frankreich= 20%, Dänemark=25%, Italien=22%. Wie ist das umsetzbar ? Bisher wird ein Artikel mit Nettopreis angelegt und diesem eine tax_class zugewiesen, in unserem Fall 19% für Deutschland. Müßte der Kunde nun, bevor er den Shop anschaut, sein Heimatland auswählen, damit die korrekte USt ausgewiesen kann (die Sonderfälle ignoriere ich erstmal) ? D.h. ein Artikel mit dem Nettopreis 1,19 Euro in D, kostet dann in F: 1,20 Euro, in DK: 1,25 Euro und in I: 1,22 Euro ? => es müßte dann den Ländern zugeordnete USt-Sätze geben und die Produkte müßten abhängig vom gewählten Land die entsprechende USt heranziehen, um den korrekten Endpreis darzustellen. Alternativ wäre es immer der gleiche Bruttopreis, also 1.19 Euro, und dann entsprechend die länderspezifische Ust ausgewiesen ? Oder habe ich das falsch verstanden ? Gibt es hierzu schon ein Addon ? mfg A. Maischein
  4. amaische

    Header Tags SEO

    Dear Jack, thanks for the fast reply. I did not realize that I should install the hybrid one, so my "Enable Keyword Meta Tag" shows only true and false. I changed it to the menu and everything works. Thank you very much
  5. amaische

    Header Tags SEO

    Hello, In product_info no "meta name=Keywords" are generated and in admin I get the following error in header tags-page control-product-info.php when i try to save the settings: " Missing sort orders are not allowed -> product_info.php " and nothing is saved in the database. When I run header tags-test for product_info, I receive several notices like " Notice: Undefined variable: id in /xxx/s4/catalog/admin/header_tags_test.php on line 563 " or "Notice: Uninitialized string offset: 1 in /xxx/s4/catalog/admin/header_tags_test.php on line 577". And as a result of the test, it is shown " product_info.php is missing data. Fill Tags should be ran. " How can I solve this problem ? PS: I use Phoenix 1077 and Header Tags 1074andlater.
  6. amaische

    Wishlist For Phoenix

    I copied the mentioned <div>...</div> to tpl_nb_wishlist.php in includes/modules/navbar/templates. Now I receive an empty page and inside I can find: <div class="dropdown-menu dropdown-menu-lg-right" aria-labelledby="navDropdownCart"> <br> <b>Warning</b>: Use of undefined constant MODULE_NAVBAR_WISH_LIST_HAS_CONTENTS - assumed 'MODULE_NAVBAR_WISH_LIST_HAS_CONTENTS' (this will throw an Error in a future version of PHP) in <b>/xx/s4/catalog/includes/modules/navbar/templates/tpl_nb_wishlist.php</b> on line <b>4</b><br> <br> <b>Notice</b>: Undefined index: wishList in <b>/xx/s4/catalog/includes/modules/navbar/templates/tpl_nb_wishlist.php</b> on line <b>4</b><br> <br> <b>Fatal error</b>: Uncaught Error: Call to a member function count_contents() on null in /xx/s4/catalog/includes/modules/navbar/templates/tpl_nb_wishlist.php:4 Stack trace: #0 /xx/s4/catalog/includes/modules/block_template.php(14): include() #1 /xx/s4/catalog/includes/modules/navbar/nb_wishlist.php(51): include('/homepages/42/d...') #2 /xx/s4/catalog/includes/modules/content/navigation/cm_navbar.php(60): nb_wishlist-&gt;getOutput() #3 /xx/s4/catalog/includes/system/versioned/1.0.7.6/osc_template.php(106): cm_navbar-&gt;execute() #4 /xx/s4/catalog/templates/default/includes/components/template_top.php(46): oscTemplate-&gt;getContent('navigation') #5 /xx/s4/catalog/templates/default/includes/pages/index.php(13): require('/homepages/42/d...') #6 /xx/s4/catalog/index.php(35): require('/homepages/42/d...') #7 {main} thrown in <b>/xx/s4/catalog/includes/modules/navbar/templates/tpl_nb_wishlist.php</b> on line <b>4</b><br> </div> I dont have anywhere the MODULE_NAVBAR_WISH_LIST_HAST_CONTENTS besides in the copied part.
  7. amaische

    Wishlist For Phoenix

    Thank you for the reply and sorry, I copied an pasted the wrong error (this one I have found). The correct error is: Uncaught Error: Call to a member function count_contents() on null in /homepages/42/d33248359/htdocs/s4/catalog/includes/modules/navbar/templates/tpl_nb_wishlist.php wishlist is uploaded in classes.
  8. amaische

    Wishlist For Phoenix

    Hello, I have Phoenix 1.0.7.7 and I dont know, how to solve the problem " Fatal error: Uncaught Error: Call to a member function count_contents() " in this version. Can you please help me ? best regards A. Maischein
  9. amaische

    Header Tags SEO

    Dear Jack, i have solved the problem. Due to a wrong language, identified by the function get_browser_language, the wrong metatags were drawn. For a quick solution I have replaced in application_top the following code: if (isset($HTTP_GET_VARS['language']) && tep_not_null($HTTP_GET_VARS['language'])) { $lng->set_language($HTTP_GET_VARS['language']); } else { $lng->get_browser_language(); } by if (isset($HTTP_GET_VARS['language']) && tep_not_null($HTTP_GET_VARS['language'])) { $lng->set_language($HTTP_GET_VARS['language']); } else { // $lng->get_browser_language(); $lng->language['directory']=german; $lng->language['id']=2; } Does anybody know why the wrong language is identified ? Anke
  10. amaische

    Header Tags SEO

    Hello, I checked the index, the header_tags, header, function-directory,etc with winmerge and the files seemed to be the same. I checked the test page with another webtool again and the tool told me, that the german page is just a forwarding to the english page. This will explain the effect. But now is the question: Why is the german page (or french page) forwarded to the english page in the metatags-checks and google search ? If you want to have a look at the side, please see this link: test german article Thank you in advance for any help. Anke
  11. amaische

    Header Tags SEO

    Dear Jack, it is the product page in the shop-area. In the os online-shop everything seems to be alright, but when you check that page via a webtool, the wrong metatags are drawn. Anke
  12. amaische

    Header Tags SEO

    Hello, I installed header_tags_seo_v_3.0.7 and everything works fine, BUT I have 3 languages in my shop (english, german, french). When I open our online-shop and look at the source code of the product_info-page, the metatags are filled in correctly, e.g. <title>article1 german title</title> <meta name="Description" content="article1 german description" /> <meta name="Keywords" content="article1 german keywords" /> If i check this german product-page of article1 with a webmaster tool regarding the metatags, the english metatags are shown. If i delete the english metatags of arcticle1, the english metatags from the page control are shown. Why are always the english metatags are shown ? What can I do, that the german or french metatags will be used ?
  13. amaische

    Recover Cart Sales

    Hello, I have just added a contribution to the Recover Cart Sales. This version saves the customers choosen language to the Table customers, when the customer creates a new account or puts some article in the basket. If you use the recover cart tool in the admin, the email to the customer is sent in the customers choosen language (not in the admin tool language). Please note: the contribution only works with new data, because i have not migrated the old data. If you have added the contrib and a new basket shows up in the RCS, you can see in the shown table under "Sprache" the language of the customer. Good luck
  14. Hallo, habe soeben ein entsprechendes Update hochgeladen. Wie ich gesehen habe, hast Du ebenfalls ein Update bzgl create_account hochgeladen. An dieser Baustelle hatte ich mir auch schon Gedanken gemacht - wenn ich es richtig gesehen habe, setzt Du den Newsletter gleich auf "Bestätigt" (newsletter_invite=2). Dies ist m.E. nicht zulässig, da der Kunde immer das Double-In-Verfahren durchlaufen muß. amaische
  15. Das sieht genauso aus wie bei mir. Ist in /catalog/inscription_newsletter.php ca in Zeile 138 folgender Eintrag drin ?: <td><?php echo $messageStack->output('inscription_newsletter'); ?></td> und beginnt die Datei mit: require('includes/application_top.php'); require(DIR_WS_LANGUAGES . $language . '/' . FILENAME_INSCRIPTION_NEWSLETTER); $error = false; if (isset($HTTP_GET_VARS['action']) && (($HTTP_GET_VARS['action'] == 'process') || ($HTTP_GET_VARS['action'] == 'confirm'))) { // Désabonnement de la newsletter $newsletter_email = tep_db_prepare_input($HTTP_POST_VARS['newsletter_email']); $newsletter_query = tep_db_query("select * from " . TABLE_CUSTOMERS_NEWSLETTER . " where customers_newsletter_email = '" . tep_db_input($newsletter_email) . "'"); $newsletter = tep_db_fetch_array($newsletter_query); if ($newsletter_invite == '0') { tep_db_query("delete from " . TABLE_CUSTOMERS_NEWSLETTER . " where customers_newsletter_email = '" . tep_db_input($newsletter_email) . "'"); $messageStack->add('inscription_newsletter', TEXT_INSCRIPTION_NEWSLETTER_UPDATE); // Envoi du mail de confirmation de désabonnement à la newsletter $email_text .= EMAIL_TEXT_NON . EMAIL_GRUSS . EMAIL_abschluss; $email_betreff = EMAIL_SUBJECT . ' ' . NEWSLETTER_BOX_NON; tep_mail('', $newsletter_email, $email_betreff, $email_text, STORE_OWNER, STORE_OWNER_EMAIL_ADDRESS); } else { // Vérification de la validité du mail Falls das auch noch nicht hilft, könnte ich mir höchstens vorstellen, daß das newsletter_invite nicht richtig übergeben wird und wie folgt ausgelesen werden muß: an der Stelle: $newsletter_email = tep_db_prepare_input($HTTP_POST_VARS['newsletter_email']); darunter hinzufügen: $newsletter_invite = tep_db_prepare_input($HTTP_POST_VARS['newsletter_invite']); amaische
×