RaptorX Posted October 12, 2017 Posted October 12, 2017 I just opened an Issue on Github found here: Issue #378 I want to verify if this is a problem or just a configuration issue... anybody else experiencing the same? Im hosting on a 1and1.com server.
0 lesley Posted October 12, 2017 Posted October 12, 2017 Have you turned on error reporting? Did it give any clue as to what the issues were?
0 RaptorX Posted October 13, 2017 Author Posted October 13, 2017 @lesley wasnt able to but weirdly enough few minutes later the store started working fine... seems like a host error to me... will mark the issue as resolved until further checks are perfomed.
0 hfxracing Posted August 16, 2018 Posted August 16, 2018 I just upgraded for 1.03 to 1.04 I did a clean & fix DB issues and now I get this 500 Error on the 3 area's listed above I did have access before I did that also the updater is not working from 1.04 to 1.05 any ideas?
0 hfxracing Posted August 16, 2018 Posted August 16, 2018 Oh I turned on the debug I get 500 error pn Performance & Modules but on payments I see this: Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; Crypt_RSA has a deprecated constructor in /homepages/31/d658016058/htdocs/modules/googleshopping/lib/phpseclib/Crypt/RSA.php on line 280 Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; Crypt_Hash has a deprecated constructor in /homepages/31/d658016058/htdocs/modules/googleshopping/lib/phpseclib/Crypt/Hash.php on line 82 Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; Math_BigInteger has a deprecated constructor in /homepages/31/d658016058/htdocs/modules/googleshopping/lib/phpseclib/Math/BigInteger.php on line 176
0 Traumflug Posted August 16, 2018 Posted August 16, 2018 Obviously a problem of this googleshopping module. Ignoring that these security relevant classes are probably pretty dated, you can try to rename these constructor methods to just __construct(... (two underscores in front). What is the constructor method? Well, the method (function) with the same name as the class. If the class is called RSA, then its old-style constructor is function RSA(.... Also identifiable by the line number given in the deprecation message.
0 hfxracing Posted August 16, 2018 Posted August 16, 2018 I don't use googleshopping so how do I remove whole thing? I should mention my shop was mirgrated from PS to 30B's
0 Traumflug Posted August 16, 2018 Posted August 16, 2018 Find it in the list in back office -> Modules & Services and select Delete from the menu. Not just Disable or Uninstall.
0 hfxracing Posted August 16, 2018 Posted August 16, 2018 See that is part of the issue when I click modules & services I get a 500 internal server Error by removing google shipping by FTP I php errors are gone on the payment link but now even that too gives a internal 500 error. any guesses like I said I used the 30 bees tool to fix & repair the db and they I used the tool under that to optimize.
0 Traumflug Posted August 16, 2018 Posted August 16, 2018 Then you have to go to the file system and remove it there. It's the modules/googleshopping/ folder. Remove it entirely, but keep a backup somewhere outside the shop. And then cross fingers this module didn't install overrides. Getting rid of them without having the module is pretty complicated.
0 hfxracing Posted August 16, 2018 Posted August 16, 2018 Done no difference still have the internal server error on the 3 sections performance,payment,Modules & services
0 Traumflug Posted August 16, 2018 Posted August 16, 2018 Which error is it now when turning on debug mode? Can't be the same as before. One can have debug mode turned on all the time until such stuff is sorted. Worst case customers see error messages.
0 hfxracing Posted August 16, 2018 Posted August 16, 2018 front end does not seem to be effected so far that I can tell it's not a busy time for me but I would like to get the whole thing sorted out. I just didn't want to loose the history on the website but maybe I should just say F it & do a fresh install.
0 datakick Posted August 16, 2018 Posted August 16, 2018 You could also try to delete class_index.php file in cache directory. Many times the stale class cache is the root cause of such issues
0 hfxracing Posted August 16, 2018 Posted August 16, 2018 @datakick nope tried your suggestion same thing was worth a shot
0 Traumflug Posted August 16, 2018 Posted August 16, 2018 One thing to try is to turn off non-thirtybees modules. There are two switches on back office -> Advanced Parameters -> Performance to do this, Disable non thirty bees modules and Disable all overrides. If the shop works with these two switches turned on, you can keep history fairly easy: Get the 1.0.6 release package. Remove folders modules and overrides entirely and replace them with the ones coming with the release. Install required third party modules again.
0 hfxracing Posted August 16, 2018 Posted August 16, 2018 I cannot access that section it`s one of the ones that gives the 500 error what if I update all the files to 1.6 and still remove the for-mentioned files and replace
0 hfxracing Posted August 16, 2018 Posted August 16, 2018 where is it kept I will pull it under logs I guess?
0 Traumflug Posted August 16, 2018 Posted August 16, 2018 what if I update all the files to 1.[0.]6 and still remove the for-mentioned files and replace Sounds like a good idea. At least if finding the problem fails.
0 datakick Posted August 16, 2018 Posted August 16, 2018 it's log for php server itself, so it's not anywhere in your tb. The location can vary. If you have some cPanel there's usually a way to access error/access logs through there.
0 hfxracing Posted August 16, 2018 Posted August 16, 2018 Well that did not work either 1.06 issues still there
0 datakick Posted August 16, 2018 Posted August 16, 2018 you need to enable php error logs to figure out where the problem is
0 hfxracing Posted August 16, 2018 Posted August 16, 2018 If I got this right it should look like this: My files are all in the Root / errorreporting = EALL logerrors = On displayerrors = On error_log = /php-errors.log This might be beyond me do I need to create the php-errors file or will the server. I uploaded it I see no change
Question
RaptorX
I just opened an Issue on Github found here: Issue #378
I want to verify if this is a problem or just a configuration issue... anybody else experiencing the same?
Im hosting on a 1and1.com server.
38 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now