Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.


  • Content Count

  • Joined

  • Last visited

  • Days Won


Kashir2000 last won the day on May 1 2020

Kashir2000 had the most liked content!

Community Reputation

29 Excellent


  • About Me
    Web developer since 2008. On Prestashop since version 1.4, switching to thirtybees :)
  • Website

Recent Profile Visitors

766 profile views
  1. So.... how is it going? Repository seems to be not updated since 1.2.0. Anything going on in background?
  2. Ok. So to debug this, please follow instructions: Download your shop onto hardDrive (direcotries: modules, classes, controllers, overrides mainly). Do not download pictures. Perform a test search for message "Approval failed" and locate which file is emitting this error. Come back, and report. Just a guess, but this may be some 3rd party module or modification integrated as override etc. Maybe some kind of CAPTCHA? Some modules can modify core controllers and classes by preg replaces.
  3. @Alex Hansen Tried to disable 3rd party modules? There is an option in Performance preferences, to disable them. Then check if works. If it works, then one one third party modules is doing something wrong.
  4. It's done only by one person. @datakick. Is he part of new crew? I thought he was volunteer. There was also his goodbye post, but he didn't go? Was he hired?
  5. @Messenger Bee is there any date you estimate for this transaction to end? Will it be month, 6 months or few years? I think it should be possible to determine when we might expect anything to move?
  6. @lovelygifts I see you enabled debugging. I see message " error in template "/home/lovelygi/public_html/themes/community-theme-default/header.tpl" on line 99 "function gtag(){dataLayer.push(arguments);}" - Unexpected ".", expected one of: "}"" That means, that in header.tpl you added gtag code. Put it between {literal} tags. {literal}Yout google code here.{/literal}
  7. I opened your site. This 500 Error has a long text there. Encrypted. You can decrypt it in Backoffice > Advanced Parameters > Logs
  8. Your .htaccess seems to be fine. Robots.txt on the other way, does not cause 500 errors. Go to your Admin Panel Performance options and Enable debug mode. Then see what 500 hides from you.
  9. @Fernando In custom CSS I would go with: body.category-{id_category} .category-info { display: none;} .category-info will hide h1 and description .page-heading.product-listing would hide only h1
  10. If you're at fixing stuff, then one thing. Just one small thing I can't watch at... or 2 rather... Pretty please... it hurts me 😞
  11. Can't quite agree here (maybe a personal matter). I think it's a company that should post such messages. Not its members. Not every member should be allowed to post official statements, so only selected ones should have access to this account. Still, this account privileges should be elevated to @Messenger Bee a minimum of credibility.
  12. There are mainly personal accounts here. So basically this account was created to post "Official" statements. Quite logical I would say (Unless there is other official account) Still, anyone could've created "Member" account. @Messenger Bee Maybe upgrade this account to Moderator/Admin etc? As long as it's a "Member" It's safe to assume it may be a troll account! On the other hand. It's interesting who wants to take this project over 🙂 @datakick already stated that he does not want. @Traumflug hmm... interesting 🙂 Praying for well being of a project 🙂
  13. Kashir2000


    @Traumflug There is also another thing. There are not many people wanting for TB to rise for one simple reason: Having to maintain compatibility for 2 shops. A lot of devs dream of 1.6 being put to rest (yes, they also hate Prestashop 1.6), as 1.7 takes over. Maintaining backward compatibility with 1.6 (and/or TB) is additional work. So basically it's not personally aimed at TB or you guys, it's aimed at lowering costs and maximizing income. Because of state of 1.7 I'm seriously thinking about changing my business model. I don't want to be held responsible by my clients for bugs in 1.7. Still, my clients I migrated to TB expect FROM ME modules for prestashop to work or fix them. Their mentality is like: "If I had Prestashop, it would surely work". So either I go on war with them or comply with their insane requests. It's a shame, but this brings a lot of regret to devs like you and me. PS: Also, when I recommend thirtybees and explain all differences, I'm being held responsible for recommending it to clients. Some people are insane, and blaming their decisions on others. And saying "Prestashop would be better". That's where "brand" part comes in.
  • Create New...