Jump to content
thirty bees forum

Mark

Members
  • Posts

    277
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by Mark

  1. I have a fresh installation of TB that I want to use with an old db.

    The working installation I have has always had things wrong (ie blog not working) so I do not want the old code base.

    Im shifting domains completely, with a fresh code base. But I do want my old database.

    Whats the suggestion here?

    • Like 2
  2. On 11/22/2019 at 7:25 PM, datakick said:

    Full Page Cache

    Ive activated FPC for all the beesblogs modules, Cleared the cache, but still no sign of the blog yet @datakick

     

    Getting a lot of errors in console on the home page

     

    [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIContentSniffer.getMIMETypeFromContent]"  nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)"  location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 277"  data: no] FaviconLoader.jsm:277:24
    Promise resolved while context is inactive
    include.preload.js:549
    Promise resolved while context is inactive
    polyfill.js:237
    [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIDOMWindowUtils.addSheet]"  nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame :: resource://gre/modules/ExtensionCommon.jsm :: runSafeSyncWithoutClone :: line 75"  data: no] ExtensionCommon.jsm:75:12
    [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMWindowUtils.removeSheet]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/ExtensionCommon.jsm :: runSafeSyncWithoutClone :: line 75"  data: no] 2 ExtensionCommon.jsm:75:12
    [Exception... "Favicon at "https://product.solutions.org.nz/img/app_icon.png" failed to load: Not Found."  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 236"  data: no] 2 FaviconLoader.jsm:236:22
    [Exception... "Favicon at "https://product.solutions.org.nz/img/app_icon.png" failed to load: Not Found."  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 236"  data: no] 5 FaviconLoader.jsm:236:22
    [Exception... "Favicon at "https://product.solutions.org.nz/img/app_icon.png" failed to load: Not Found."  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 236"  data: no] 3 FaviconLoader.jsm:236:22
    [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMWindowUtils.removeSheet]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/ExtensionCommon.jsm :: runSafeSyncWithoutClone :: line 75"  data: no] 3 ExtensionCommon.jsm:75:12
    [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMWindowUtils.removeSheet]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/ExtensionCommon.jsm :: runSafeSyncWithoutClone :: line 75"  data: no] 2 ExtensionCommon.jsm:75:12
    [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMWindowUtils.removeSheet]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/ExtensionCommon.jsm :: runSafeSyncWithoutClone :: line 75"  data: no] 2 ExtensionCommon.jsm:75:12
    [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMWindowUtils.removeSheet]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/ExtensionCommon.jsm :: runSafeSyncWithoutClone :: line 75"  data: no] 2 ExtensionCommon.jsm:75:12
    [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMWindowUtils.removeSheet]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/ExtensionCommon.jsm :: runSafeSyncWithoutClone :: line 75"  data: no] 2 ExtensionCommon.jsm:75:12
    [Exception... "Favicon at "https://product.solutions.org.nz/img/app_icon.png" failed to load: Not Found."  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 236"  data: no] FaviconLoader.jsm:236:22
    [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMWindowUtils.removeSheet]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/ExtensionCommon.jsm :: runSafeSyncWithoutClone :: line 75"  data: no] 2 ExtensionCommon.jsm:75:12
    [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMWindowUtils.removeSheet]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/ExtensionCommon.jsm :: runSafeSyncWithoutClone :: line 75"  data: no] 2 ExtensionCommon.jsm:75:12
    [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMWindowUtils.removeSheet]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/ExtensionCommon.jsm :: runSafeSyncWithoutClone :: line 75"  data: no] 2 ExtensionCommon.jsm:75:12
    [Exception... "Favicon at "https://forum.thirtybees.com/favicon.ico" failed to load: Not Found."  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 236"  data: no] FaviconLoader.jsm:236:22
    [Exception... "Favicon at "https://product.solutions.org.nz/img/app_icon.png" failed to load: Not Found."  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 236"  data: no] FaviconLoader.jsm:236:22
    [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMWindowUtils.removeSheet]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/ExtensionCommon.jsm :: runSafeSyncWithoutClone :: line 75"  data: no] 2 ExtensionCommon.jsm:75:12

     

  3. Im not repeating myself, the problem does not yet require under the hood attention, and so its access is not being given.

    In terms of honour, do what you say you are going to do, or apologise you can no longer do it.

    Its not about who is being paid and who is not, its about trust and doing what you say.

  4. The story @datakick is that at this stage no access to the backend is required. Given that I've done nothing to the codebase I'm presuming there's nothing wrong with the code and it's just something I haven't spotted yet.


    I don't give strangers access to any data for no reason and that's a key principle I would suggest others follow.


    If there's a problem with the code then it becomes a different story.

     

    I'm not talking about Skype but I am talking about screen sharing using team viewer where zen and his infinite wisdom can show me the button I am yet to press.

     

    Don't try to nail me for having expectations around what I will permit others to be able to do on the site, everyone has that total right.

    I don't even know who zen is, never spoke with him in a conversation as if I'll let anyone into any system like that. He offered to help then never replied when I sent a pm.

     

    That's fine, just say so man, it's not hard to say sorry I changed my mind, much better manners than ignoring.

     

     

     

     

  5. There's times when logging in is necessary, this is not one of them. It's a case of screen sharing. Don't get all offended and respect a few things about others, including responding and doing as you say as well as data privacy.

  6. No worries, you'll not be logging in, there's no need to.  I don't give randoms any unnecessary access when not required.
    I don't often get the time to work on this site.

    It's the blog that's that not functioning, that's all

    Probably just a button somewhere that's escaped my attention.

     

     

  7. CONSOLE:

     

    Loading failed for the <script> with source “blob:https://product.solutions.org.nz/4d36e740-8dfb-4afe-a1f7-1ba2157fd731”. index.php:1:1
    The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it. enquire.min.js
    The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it. admin-theme.js

     

    Network attached as HAR @datakick

    Edited by datakick: removed HAR file, as it contains sensitive information

     

  8. It's possible the connection type or speed or perhaps IP address might have something to do with this @datakick when I was on "true wifFi", an actual wiFi connection today it worked fine, with the Save function fine, this evening I'm on "Wifi" but its actually a WifI connection to a phone thats running cell data... and the Save in products does not work again, everything else is the same... apart from the connection.

    It doesnt work regardless of device/ browser

     

     

  9.  

    5 minutes ago, SLiCK_303 said:

    Bleeding Edge is just that, the latest changes, so problems will on occasion come up.  If it's been awhile since you upgraded to BE, I recommend you run the updater again, and see if there are any file changes

    I ran the updater about 10 minutes ago, cleared the cache, logged out. logged in.

    Ive been on BE probably 4-6 weeks now, because there are issues in cauterised edge I cant go back to

    Still the same.

  10. On 10/31/2019 at 6:53 PM, Pilou said:

    Hello Mark,

    I thought like you, but I see that many founders have already left the ship.
    I am still in the testing phase, but I hesitate more and more to take the step...

    @Pilou PS/ TB is complex and trying to do something large, so Ive tried to cut slack, but I always get this "its your server" nonsense and there it ends, without any clue as to what this apparent issue with my server is. Things dont work when they did just days before with no server changes so I am pretty sure its an excuse to get rid of the complainant. I have a list of about 30 things that are frustrating, although there is a work around for most. However this one is terminal.

    Ive also put things into github that started out promisingly but never got done properly and all issues I have reported still remain.

  11. On 10/31/2019 at 7:45 PM, datakick said:

    We can fix only things that can be reproduced. I support lots of thirtybees shops, and not one of them has this issue. If you don't believe me, you can test it on my demo server account here. This problem is also not reproducible on vanilla installation. That all lead to conclusion that this is issue with your specific installation - some third party module, server issue, or what not. 

    @datakick I newly established TB not long ago at 1.0.8 and have done ll the upgrades since, so my codebase is not far from fresh, and have never interfered with any code except to add php.ini and phpinfo. I run bleeding edge. It was running fine on my server and then it was not and still isn't.  If the server has not been touched, how can that be the server if once was that was fine? The only thing that has changed is the code. Clearly others have also had the issue. Whenever I talk to you thirtybees guys its always "the server" and everything stops there.

    As a side comment, I dont why php.ini isnt established in the code base.

     

    Quote

    We are happy to fix bugs that can be reproduced, ideally on vanilla installation. If you can describe the steps how to reproduce the issue, it will be fixed.

    Steps to reproduce are: Go to to any product page. The Save buttons are constantly spinning. There is no way to Save.

    Quote

    It is true that *serious bug* regarding ever-spinning button was commited into 1.1.x branch - bleeding edge. It affected only those people who upgraded to bleeding edge after Oct 8. (Note that the problem originally reported in this forum thread was NOT caused by that bug. Simply because the user did not run on bleeding edge, and also it was reported on Oct 7).

    This bug was discovered (reported to github) on Oct 21. I guess not many merchants updated to bleeding edge between Oct 8 and Oct 21 - I would assume such a serious bug would be reported sooner.  The fix was implemented on Oct 21 -- yes, it took whole zero days to fix this, since it was reported.

    I don't know, but I don't think this is *blaming something else instead of providing solutions*

    Blaming servers for this and walking away from it leaving users to work it out for themselves is not cool. Thats not a solution. I realise you cant fix everything, there's so much to do and you are only human, but this one is terminal with no work around.

    It did not take zero days to fix. Its still broken. This Post was first made on Oct 8

    There should be some sort of "server test" for an issue that we can undertake if you believe it could truly be a server issue, so that we have something to resolve things, never have them hang.

    Here I m trying to get products editted and loaded and its impossible right on Christmas time.

    Quote

    Of course, this kind of bug should never made it into 1.1.x branch in the first place. But it did. We devs are only people, and things like this happens sometimes. Thankfully, this was never *officially* released, as bleeding edge is not an official release version. 

    I have even more issues if I dont use bleeding edge so I am forced to use this (under your recommendation from another post)

     

  12. Can we quit with accusations of hosting being the problem in order to avoid fixing issues please?

    No its not, My Save buttons do not work either and they did before

    Ive just Updated via Core Updater, cleared caches and the problem remains.

    What kind of testing gets done round here, when there are terminal issues like this occuring and there's an attitude by the senior devs to blame something else instead of providing solutions? Days ago this was reported and now its a blame game and no fix.

    I came to thirtybees because the attitude was stated as NOT being like Prestashop, that there was a commitment to fixing things.

     

    Im trying to load a whole bunch of products into the system, and I cannot do the basics. Some things automatically save when you dont want them to, others cant be saved (such as shipping) and the buttons are endlessly spinning

     

    As of yesterday, I withdrew my support for thirtybees because of this attitude plus the culture of not manning up to things that have been committed to and communicating professionally

  13. It still sends via smtp using PHP mailer and therefore that is working fine from a TB point of view but of course ends up in spam etc, so I'd prefer to be using a mail sending service.

    Despite entering valid credentials and trying a range of port options, it wont connect to either Sendgrid or MailJet, who send back the same fail responses as each other, indicating the problem might well be at my end with TB code, or something on my server I haven't needed to do so far on other projects.

    Surely others must have this problem also, as I very much doubt anyone is using PHP mailer.

     

  14. Hi, blog doesn't seem to be working on my site.

    I have the following modules installed and here's the config

    The blog doesn't show up on the home page (or anywhere else)

    However if I manually type in <site name>/blog/<blog url rewrite> it is there, but is missing the related products etc.

    Maybe one for you @wakabayashi?

    However if use the url image.png.c65882c15c5c4b3edcbcc5adddb1dcb9.png

    Capture.PNG

×
×
  • Create New...