Text only | Text with Images

ElkArte Community

Elk Development => Bug Reports => Exterminated Bugs => Topic started by: badmonkey on December 10, 2017, 08:50:31 pm

Title: Current github version results in 500 error
Post by: badmonkey on December 10, 2017, 08:50:31 pm
php7, vanilla download, unzip, and upload results in a 500 error.    :P
Title: Re: Current github version results in 500 error
Post by: Spuds on December 10, 2017, 10:32:39 pm
Please check your server and/or php error logs and see what it tripped over.  There should be an obvious error in them for a 500.

Thanks!
Title: Re: Current github version results in 500 error
Post by: badmonkey on December 11, 2017, 12:22:28 am
Sorry, was moar interested in restoring a backup on a production site. Then the outcome of the Pittsburg game.   ;D ;D


Anywho, I think this is the correct place in the log.   ;)



QuoteStack trace:
#0 /var/www/clients/.../web/sources/subs/Errors/Errors.php(298): ElkArte\Themes\ThemeLoader->__construct()
#1 /var/www/clients/.../web/sources/subs/Errors/ErrorHandler.php(167): ElkArte\Errors\Errors->_setup_fatal_ErrorContext('Class 'ElkArte\\...', 0)
#2 [internal function]: ElkArte\Errors\ErrorHandler->exception_handler(Object(Error))
#3 {main}
  thrown in /var/www/clients/.../web/sources/subs/Themes/ThemeLoader.php on line 429" while reading response header from upstream, client: IPaddy, server: xx.com, request: "GET /index.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9011", host: "www.xx.com"
Title: Re: Current github version results in 500 error
Post by: ahrasis on December 11, 2017, 12:38:50 am
You mean the development version @badmonkey?[1]
1 Release version of 1.1.0 and then the patch for 1.1.1 is working fine for me.↵
Title: Re: Current github version results in 500 error
Post by: badmonkey on December 11, 2017, 12:43:02 am
Yes. I was behind a few commits. The plan was to upload the current development, then apply the patch. Was this incorrect?
Title: Re: Current github version results in 500 error
Post by: ahrasis on December 11, 2017, 12:50:44 am
I think the patch is meant for 1.1.0 and not the development version. I also got error when using development version, so I override it with 1.1.0 then I use 1.1.1 patch. So far this work for me.
Title: Re: Current github version results in 500 error
Post by: emanuele on December 11, 2017, 02:26:23 pm
development is already behind 1.1, it's what will become 2.0 (and it may be broken).
master is the stable version (that right now is 1.1.1).
master was 1.0 until before 1.1 was released, then it switched to 1.1 and.
development was 1.1 until 1.1 was released, then it switched back to "real" development for the next version.

So, what do you have now and what do you want to do? :P
Title: Re: Current github version results in 500 error
Post by: Jorin on December 12, 2017, 05:48:24 am
A little help if you got lost...

(Link-5338)
Title: Re: Current github version results in 500 error
Post by: emanuele on December 12, 2017, 07:09:53 am
Not sure why 2.0 goes to the trash bin, though. xD
Title: Re: Current github version results in 500 error
Post by: Jorin on December 12, 2017, 07:34:48 am
You said so.  :D
Title: Re: Current github version results in 500 error
Post by: emanuele on December 12, 2017, 09:01:07 am
xD

BTW this is the original article about the branching model:
http://nvie.com/posts/a-successful-git-branching-model/
Title: Re: Current github version results in 500 error
Post by: badmonkey on December 12, 2017, 05:08:26 pm
Quote from: emanuele – So, what do you have now and what do you want to do? :P

I want to enjoy life as much as possible, hopefully with friends who will as well. Regarding elk, I think that clears it up.  lol.

Seriously, staying up on the latest code fixes is desirable here. So the Development branch should be ignored until it becomes 2.0, or at least not comingled with 1.1.x?
Title: Re: Current github version results in 500 error
Post by: emanuele on December 12, 2017, 06:06:31 pm
LOL

You should keep up  with master, that's the most stable up-to-date version. Anything else may provide you surprises along with novelties. xD
And next time a 1.1.x is needed (i.e. 1.1.2) a new branch "patch_1-1-2" will be created, at that point you may want to peek there to have the "edge of the stable" (i.e. a sort of beta :P).
I hope it makes sense because I'm pretty much sleeping right now so I'm not sure what I'm writing. xD
Title: Re: Current github version results in 500 error
Post by: ahrasis on December 12, 2017, 06:51:52 pm
Just use the release version for your live sites @badmonkey. No need to rush for the one that is not yet released, whether there is some new fixes or not.

The unreleased version can be used on any of your test sites.
Title: Re: Current github version results in 500 error
Post by: badmonkey on December 12, 2017, 07:20:15 pm
That would be the intelligent thing to do. But what fun is that? ;D  Then, there is the internal dialogue. Imagine the cartoon angel on one side, devil on the other. "No, it isn't safe yet". "Oooo! New features!" Exactly. Besides, if not for those of us living dangerously, who is to aggravate you about bugz?   :D


Seriously, thanks for all the work you guys put into Elk. It creates virtual homes for many people. 8)
Title: Re: Current github version results in 500 error
Post by: emanuele on December 13, 2017, 02:33:32 am
ROFL!
/me starts thinking emoji are an interesting addition to consider. O:-)
Title: Re: Current github version results in 500 error
Post by: ahrasis on December 15, 2017, 03:58:24 am
I thought you wanna remove every features and then rewrite everything @emanuele... :P
Title: Re: Current github version results in 500 error
Post by: emanuele on December 15, 2017, 06:13:25 am
naaa.... rewrite is a waste of time.
Refactor is hundreds of times better and easier! :D
Title: Re: Current github version results in 500 error
Post by: live627 on December 15, 2017, 06:41:31 am
But how does one refactor the user?
Title: Re: Current github version results in 500 error
Post by: emanuele on December 15, 2017, 07:38:17 am
You mean the $user_info/settings mess, or the persons behind? :P
Title: Re: Current github version results in 500 error
Post by: live627 on December 15, 2017, 04:13:36 pm
/me refactors @emanuele  :D
Title: Re: Current github version results in 500 error
Post by: emanuele on December 15, 2017, 04:53:43 pm
Good luck with that! xD
Title: Re: Current github version results in 500 error
Post by: live627 on December 15, 2017, 07:04:05 pm
To refactor, press  any  key.

(http://www.tostartpressanykey.com/wp-content/uploads/2014/04/homer_1200b-1038x576.jpg)
Title: Re: Current github version results in 500 error
Post by: emanuele on December 15, 2017, 07:05:08 pm
/me doesn't have an any  key on this keyboard...
Title: Re: Current github version results in 500 error
Post by: live627 on December 15, 2017, 07:28:50 pm
The internets wouldn't lie to me, right? Right?

(https://johnfudrow.files.wordpress.com/2007/07/any_key.jpg?w=500&h=375)
Title: Re: Current github version results in 500 error
Post by: badmonkey on December 15, 2017, 08:12:23 pm
/me is glad you guys aren't overly serious


Title: Re: Current github version results in 500 error
Post by: live627 on December 15, 2017, 09:35:13 pm
(http://i0.kym-cdn.com/photos/images/facebook/000/048/811/Breadcat.jpg)
Text only | Text with Images