Jump to content
thirty bees forum

Purity

Members
  • Posts

    104
  • Joined

  • Last visited

Everything posted by Purity

  1. I just realized I have a huge problem after updating to 1.0.8 after the last update with the old updater. My entire logo/header/menu is gone on specifically mobile. Works perfectly on desktop. If I re-update with this module would this possibly fix this, or do you have any idea what may have caused this?
  2. @coffeeguy said in Page not found - loads, every day: OK! That's some of them that have been coming up in that "Who's online" thing. How do I get rid of them??! Where did they come from? THANK YOU! One step closer - but why are they there? https://bryankollar.com/coffeeguy/modules/themeconfigurator/img/d3b50e40ab8895f3e209ac060395256f65264569voiceofkatie.jpg https://bryankollar.com/coffeeguy/modules/themeconfigurator/img/431901dfc80ee98659aedb0a52d5dc93b9ad4c42voicewebsitelogo.jpg The first 2 seem to be a part of/editable in the theme config module. Did you look to see if there's anything related to those in there? I checked, and these 2 links are indeed in the html of your main store page. I do not have a plain/vanilla themed installation so I cannot look into this further. I actually couldn't find most of these "1" links on the pages they are supposedly linked from. Perhaps somebody else might know what that is about.
  3. I can't tell you what any of these are, because I do not have access to your installation, but here is a list of 404's on your website. You seem to have a 404'd logo of some sort and some weird "1" pages...not sure what those are. You can use a broken link checking tool to find such 404's. https://bryankollar.com/coffeeguy/modules/themeconfigurator/img/d3b50e40ab8895f3e209ac060395256f65264569voiceofkatie.jpg https://bryankollar.com/coffeeguy/modules/themeconfigurator/img/431901dfc80ee98659aedb0a52d5dc93b9ad4c42voicewebsitelogo.jpg https://bryankollar.com/coffeeguy/1 https://bryankollar.com/coffeeguy/search-by-brand-name/indulgio/1 https://bryankollar.com/coffeeguy/search-by-brand-name/1 https://bryankollar.com/coffeeguy/search-by-brand-name/starbucks/1 https://bryankollar.com/coffeeguy/search-by-brand-name/gevalia/1 https://bryankollar.com/coffeeguy/search-by-brand-name/ripafratta/1 https://bryankollar.com/coffeeguy/search-by-brand-name/winter-wonderland/1 https://bryankollar.com/coffeeguy/search-by-brand-name/entenmanns/1 https://bryankollar.com/coffeeguy/search-by-brand-name/crazy-cups/1 https://bryankollar.com/coffeeguy/search-by-brand-name/friendlys/1 https://bryankollar.com/coffeeguy/search-by-brand-name/guy-fieri/1 https://bryankollar.com/coffeeguy/search-by-brand-name/dunkin-donuts/1 https://bryankollar.com/coffeeguy/search-by-brand-name/skinny-girl/1 https://bryankollar.com/coffeeguy/search-by-brand-name/lipton/1 https://bryankollar.com/coffeeguy/search-by-brand-name/grove-square/1 https://bryankollar.com/coffeeguy/search-by-brand-name/chock-full-o-nuts/1 edit * looks like you found out about broken link checkers around the same time I posted this.
  4. @wakabayashi said in Major problems: Search does not work after update to 1.0.8: @Purity he is using elasticsearch and you are probably (?) using the normal search. But his reaction is not legitimate: 1. lesley offered help, but he doesn't want to give access 2. he is using elasticsearch, which needs quite a bit knowledge to handle it. 3. he "threats" to go back to ps. after all since when does ps offer elasticsearch? I am indeed using the normal search but unless I misunderstood something he said he uninstalled elastic search and couldn't get the regular search working either.
  5. My search works perfectly fine after performing the same update from 1.0.7 to 1.0.8. If you are having problems with an update, it is likely something specific to your installation setup.
  6. Not sure why this needs said again, but if you are updating your shop, you should take a backup and/or test the update on a non-live copy of your site. There should never be a time where you update your site and then need to frantically ask for help to get your site back up. If you have problems, you should simply roll back and await a fix. You're liable to run into such problems updating even a CMS like WordPress...
  7. Purity

    Full Page cache

    I believe you should keep it turned off for now. It hasn't worked for me in recent versions of TB.
  8. This one looks nice. Might give it a shot sometime. I used to use this one but TB payment options wouldn't show up for me with it. https://addons.prestashop.com/en/express-checkout-process/6841-one-page-checkout-for-prestashop.html
  9. Have no problems with warehouse but I only use it because I've used it essentially since it came out. Works perfectly with TB and the developer is a nice guy but as other people have said, he's working solely on PS 1.7 now. Since he's not updating it anymore for our implementation, I cannot recommend it, but it does work well at the moment. I'd imagine out of these 3 options you would want to go with Panda.
  10. @Traumflug @lesley If this is the case (which it appears to be) would it be a good idea to add this to the PayPal documentation? https://docs.thirtybees.com/native-modules/paypal/ ^^^ Gives no mention of only supporting up to php 7.0
  11. @haylau said in Paypal authentification details error on 5.3.3 but not on 6.0 beta: I think there are problems. I could authenticate but not checkout. I linked it to PHP, I narrowed it down to PH7.0 works, anything higher does not https://forum.thirtybees.com/topic/2283/paypal-errors @purity said in Paypal authentification details error on 5.3.3 but not on 6.0 beta: @haylau said in Paypal authentification details error on 5.3.3 but not on 6.0 beta: I think there are problems. I could authenticate but not checkout. I linked it to PHP, I narrowed it down to PH7.0 works, anything higher does not https://forum.thirtybees.com/topic/2283/paypal-errors Thanks, I'll give this a try when I get a chance. I believe I am running 7.1 at the moment. Hey, thanks a lot. Seems to work great with php 7.0 I've been trying to get this working for 6+ months. I really appreciate your response. Great stuff.
  12. @haylau said in Paypal authentification details error on 5.3.3 but not on 6.0 beta: I think there are problems. I could authenticate but not checkout. I linked it to PHP, I narrowed it down to PH7.0 works, anything higher does not https://forum.thirtybees.com/topic/2283/paypal-errors Thanks, I'll give this a try when I get a chance. I believe I am running 7.1 at the moment.
  13. Every now and then I try to get this PayPal module working. The beta 6 works for me but I was told it isn't suitable for a live shop. The 5.3.3 says there is an authentication details error, despite the same details working in the 6.0 beta. Followed the TB documentation. I've also setup PayPal modules before and never had a problem getting them working. The codes are taken from the PayPal rest api section. No other errors show up, in debug mode, or regardless. Stripe works great but I would love to accept PayPal again. Is anybody able to provide insight into this? Unsure about using the mollie module, as I read it takes users offsite to mollie website?
  14. Purity

    SEO Module

    I don't have any experience with this specific module but generally it is best to do them yourself. Google does scrape this data itself from your page if none is provided. I wouldn't personally spend money on such modules. Also, that module has not been updated since 2016. Is there specific functionality here you like?
  15. I'm using warehouse on 1.0.7 as well and I don't seem to have this issue.
  16. @datakick said in Release 1.0.7 is there!: @Purity, could you please try this: toggle all hooks from red state to green, then enable Full Page Cache again, and test the front end again? I'm afraid I know where the problem is. If my hunch is correct, that would probably mean that Full Page Cache is beyond saving... Seems to work fine with everything toggled green. May I inquire as to what this might mean? lol
  17. @datakick When full page cache with debug mode on, this pops up when trying to access, specifically, subcategories. I can access homepage/categories/products/everything else just fine, but subcategories give me either 500 error or a half loaded page +500 error. Everything works fine with no error when full page cache off. So path like this Home--->Category--->subcategory (this gives 500 error) ERROR 2018/09/28 - 12:52:33: Modulo by zero at line 156 in file cache/smarty/compile/82/2d/37/822d37f7335ec005296c8431c06f098c9a68d082.file.product-list.tpl.php I was on TB 1.0.4 before and full page cache was working perfectly fine.
  18. Where is the correct place to report an issue with the full page cache? It's sending certain pages to 500 error on my installation. I did delete the cache/class_index.php
  19. @lesley Thanks a lot Lesley. I saw that before but wasn't sure if it was still applicable. I got the update installed using that guide. Looking good so far.
  20. Is there any documentation on how to manually upgrade my installation to this version? The update module didn't work for me, presumably due to shared hosting. Currently on 1.0.4
  21. Thanks for fixing the permissions issue @doclucas I don't use a lot of third party modules outside of my theme & TB modules anymore but I have added a couple modules I have tried.
  22. I have a few problems with the default robots.txt and I would appreciate some help if anybody knows how to fix these issues. I recently remade my robots.txt within TB and since then it is indexing every image as a single page, so 1,000+ blank (image only) indexed pages hit my GWT. I cannot find these pages within google but they hit google webmaster tools and crawling programs. Isn't this weird? Any ideas? They hit GWT literally overnight. The default robots.txt blocks search parameters but this block also blocks pages that have 'search' in the name for example. So, if I had a book that says 'A search for freedom', for example, it would not be indexed. I removed a line, and pages index fine, but would you guys like me to provide data about this? It blocks module access by default, which seems to block footer image indexation on warehouse theme. (I had to remove this line) This one doesn't need any fix I suppose, but I am wondering why it blocks /module by default?
  23. Well, I talked to my brother, and while he does remember the issue, sadly neither of us remembers exactly what he did to fix it. Sorry I cannot help you guys with a solution.
  24. @traumflug I sent him a message on facebook and asked but I'm not sure if he will remember. It was well over a year ago. Will update back if he remembers. It is not a TB specific issue though, whatever it was/is.
×
×
  • Create New...