Jump to content
thirty bees forum

rubben1985

Members
 View Profile  See their activity

  • Posts

    436

  • Joined

  • Last visited

  • Days Won

    11

 Content Type 

Posts posted by rubben1985

    error 500 when activating debug mode

    in Technical help

    Posted

    On 1/5/2019 at 11:30 AM, datakick said:

    @rubben1985 these particular changes are fine. We don't know, of course, how does the external file look like.

    I really think that some module or vendor library introduces class named Validate, and that this class gets loaded at the very beginning of the request. That would prevent loading Validate core class, and results in this kind of error. Search for class Validate

    With the forum migration I lost notifications and I did not saw the post...

    Any advice on how to identify/find this?

    error 500 when activating debug mode

    in Technical help

    Posted

    anyone with programming knowledge can tell me if I did something wrong with the code I introduced in the validate file? (code was to make work a module). In the actual state when I activate debug, site breaks so I can not use it but I need the code inside the file (but maybe I made something wrong even if the module now it works)

    java script error

    in Technical help

    Posted

    Cache also has problems and when it is activated, it changes the web appearance (fonts in different colors, css...). I tried to delete cache at backoffice and also manual.

    Chrome console shows some errors: When cache is not activated, appearance is correct and some errors appear:

    0_1546192934928_226727f2-c4e8-4b1a-862f-74d8d3e6fc4a-image.png

    When cache is activated, appearance is wrong and this are the error that chrome console shows (1 error more):

    0_1546193019687_0167e25c-7a1c-40b7-ac91-eea23563f674-image.png

    Any ideas?

    thirty bees getting better and better: release 1.0.8

    in Announcements about thirty bees

    Posted

    @violinparts but you understand you are asking him almost an impossible isn't it? To solve a problem but at the same time not giving him access. Some problems can be solved from outside, some don't. I am not a technician so I do not know what case this is. Anyway, you can create a profile to allow him entering into the back-office but not for example in the "clients section". That should work for you.

    java script error

    in Technical help

    Posted

    Hi,

    I use visual composer and today a new problem appeared (this problem could be there in the previous 2 weeks or so, but not before). I realized that depending on the user, navigator and private mode or not, it creates an error that blocks the editor so it doesn't work. It is not about cookies as private mode also creates the error. As I did not updated the module** in the last few months is strange for me that now, it doesnt work from one day to another.

    The hosting technical service, tells me is a javascript error with the jquery library. No idea what does it means hahaha but could this have relation with some recent module updates? I update them the days before to the 1.0.8 release (I still have 1.0.7 version, I only updated the modules). Could this have an impact? It seems difficult to be that but I do not find another update or modification in the last 2 weeks.

    It is quite curious because the error is not "regular". User 1 in chrome works fine User 1 in chrome and private mode does NOT work. User 2 in chrome doesn't work. User 2 in mozilla works in my computer, but it doesn't in another computer

    It seems like a cookie issue but User 1 does not work in private mode :/ and I have clean cookies and cache a few times

    Any idea? this is the screenshot of the error when it doesnt appear the editor screen

    0_1545942248391_c91e5592-e723-4d4f-9dc7-58fac20ded60-image.png

    ** I updated the module, update broke some things, so I restored the backup. In theory now is like it has been since months

    error 500 when activating debug mode

    in Technical help

    Posted

    Hi,

    I am having some issues with visual composer module so I activated debug mode trying to find the problem. When I activated it since the backoffice, this happened:

    0_1545930950942_47edacb6-d569-4175-ae46-2957fcfd126b-image.png

    this was the server log: 0_1545930981828_01826541-19bf-49db-9f5b-76aa49d5deff-image.png

    The hosting technical service deactivated the debug mode because I could not access to the backoffice.

    Any ideas why debug mode made this when I activated?

    Thanks

    Update to 1.0.8 Shows 500 Server Error

    in English

    Posted

    @datakick said in Update to 1.0.8 Shows 500 Server Error:

    @rubben1985 this philosophy is not new, and it's used in every software I know. It's called exception handling, and the gist is simple - if the code discovers an error, and can't safely recover from it, then it should throw the exception and transfer the responsibility to the caller. That's the best way to deal with this problem I know of, and I've been developing software for 20 years now.

    When we throw an exception in the code, we do it because we really don't know how to solve the situation at hand. Imagine if you received an email order for product you don't sell. Would you just send different product to the customer?... Because this is what you are asking thirtybees to do -- to ignore the problem and carry on like noting happened. But something happened, we know that much.

    @datakick but you can just send a message to yourself, or inform the client (if that is technically possible). No necessary to fall down the web. This only creates a bad image of the platform. In addittion you will earn almost nothing because if that happens, the owner, the first thing it will do (unless traffic is tooooo low) is going to be to restore backup immediately. When he restores, we will have a bad impression, fear to update again, and you will not have the error to analyze it because it is already restored. I can not find the good side in a production environment to be honest

    Update to 1.0.8 Shows 500 Server Error

    in English

    Posted

    @datakick I cannot agree with this. Will it help to discover bugs? Sure. Does it justify to turn down a site. NOT AT ALL. ZERO. You have to find another method, if not medium-big merchants will run away. This is a horrible approach. Enable notifications, even enable a checkbox to send you the error. The bug is huge? well, the site owner will know there is a bug and he will decide to run or not during you fix that bug. Time will be the same (if TB takes care of the bug) and you do not put the merchant into the stress of a falling site (in some cases, that can cause thousands of dollars). I will be really clear and honest. I love TB, I have been here since almost the start, and my product will be launched in 2019. If this philosophy of "falling down to discover and repair" continues as soon as it makes me site falling and I lost orders, I will change the platform. Not only for the money and brand image (if you have high traffic can be a huge impact) but also because I do not want to pass over the stress that a fallen site means.

    Mailchimp module fetches not-confirmed newsletter subscribers in case of opt-in

    in MailChimp

    Posted

    @vsn said in Mailchimp module fetches not-confirmed newsletter subscribers in case of opt-in:

    @rubben1985 I do actually the same, but I would like to have a sync feature. Now I manually unsubscribe in back office the customers, who performed un-subscription via Mailchipm. Are you using the same approach?

    right now, as I am sending the emails with mailchimp, I am not unscribing the customers in the backoffice. To be honest I did not know, that the unscribing customers did not unscribe in the backoffice list but as mailchimp will not send the email anyway...

×
×
  • Create New...