![[HSX] HeadShot Xtreme is officially recognized by the Central Outpost as a genuine gaming organization.](https://www.headshotdomain.net/files/coRpSE/cnopseal_X74-MEW1.png "[HSX] HeadShot Xtreme is officially recognized by the Central Outpost as a genuine gaming organization.")
Search found 24 matches
Author
Message
Topic: Evo Xtreme 2.0.9e Released
Forum: PC & Codeing Talk Posted: Wed Nov 20, 2019 4:03 am Subject: Re: Evo Xtreme 2.0.9e Released
— zardos wroteHi lasermail
I think Xampp is better than Wampserver, but another one that i use is Ampps and comes with i lot of extra features, plus easy to get up and running and to manage.
Please login to see this link
Get registered or Log in
Thank you for the response zardos, that is very much appreciated. I downloaded both Xampp and Amppps after reading your post and had a quick look around. I settled on sticking with wampserver.
— coRpSE wrote
I will look into that since I use Wamp a lot.
Thank you, I find your video tutorials very helpful. Looking at the updating ones I recognized the value of testing on a localhost - I have a lot of historical stuff I don`t want to lose or corrupt. If you recall I think the last time I updated my site I ended up with overlapping fragments of old and new which gave my error logs a workout.
Topic: Evo Xtreme 2.0.9e Released
Forum: PC & Codeing Talk Posted: Tue Nov 19, 2019 11:42 am Subject: Re: Evo Xtreme 2.0.9e Released
Finding time to explore an update to 2.0.9e.
Been watching your video Tutorials. I would like to test things using Wampserver64, but as a new user I am struggling to find relevant guides or a simple tutorial on how to prepare Wampserver64 specifically for Evo Extreme testing. I have searched in vain through countless videos relating to wampserver64 and have at least installed it, exported my database, copied my www folder? (not sure what or how much) but thereafter I cannot find a guide pinpointing what else needs to be done - my localhost is simply not connecting to my database. It is likely I have yet to complete a few more simple steps. There are scores of guides by most are spoken in poor English accents or are skipping some basics?
Please consider making a short tutorial video limited to how to set up Wampserver for Evo Extreme testing purposes. Or even a short step by step guide.
Many Thanks
Been watching your video Tutorials. I would like to test things using Wampserver64, but as a new user I am struggling to find relevant guides or a simple tutorial on how to prepare Wampserver64 specifically for Evo Extreme testing. I have searched in vain through countless videos relating to wampserver64 and have at least installed it, exported my database, copied my www folder? (not sure what or how much) but thereafter I cannot find a guide pinpointing what else needs to be done - my localhost is simply not connecting to my database. It is likely I have yet to complete a few more simple steps. There are scores of guides by most are spoken in poor English accents or are skipping some basics?
Please consider making a short tutorial video limited to how to set up Wampserver for Evo Extreme testing purposes. Or even a short step by step guide.
Many Thanks
Topic: [SOLVED] Error log lodger
Forum: Nuke Blocks / Modules Support Posted: Thu Sep 27, 2018 2:02 am Subject: Re: [SOLVED] Error log lodger
— coRpSE wroteOkay, here is an update. His site has been solved. I don't know if previously he was running a older version of the CMS, or added some bad files from a "update" patch, but they were wrong. He installed fresh files from a new download and it worked, except for his admin which turned out to be some bad links placed into the "Modules Block EDIT", (for the navigation he was using). I removed those links and everything worked fine. I did suggest to him to use Sommaire which is what is used on this site instead, and it is preinstalled with the CMS so it's worth using.
Link to the tutorial is here:
Please login to see this link
Get registered or Log in
...and very much appreciated has been your skilled understanding, advice and daily replies.
I have been running game servers over 15 years and some years back created a Nuke Evo website. As a Nuke Evo user I would teach myself some basics, get things to work then let sleeping dogs lie. I rarely made many changes once the site worked and suited its purpose. However I have been forced to recover from serious mess ups by my web hosting company three or four times over the years (they wiped a lot of forum history and forum members). Likely each time I thought I was recovering things were actually getting more out of tune. So one error, compounded another and so on. I think this is the first time I found a really reliable source of working files and people able to offer valid help. Over the years there have been several websites claiming to support the Nuke Evo community, but these appear to have shrunk in number considerably of late - many people have moved to use other things - not all look that convincing imo. Â
Ultimately it has taken a person with valid and up to date knowledge to recognise the exact nature of the problems on my website, and then finally step in with the hands on fixes.
THANK YOU VERY MUCH.
Topic: [SOLVED] Error log lodger
Forum: Nuke Blocks / Modules Support Posted: Wed Sep 26, 2018 4:19 am Subject: Re: Error log lodger
— coRpSE wroteokay.
Apologies this is long winded, but concise. It is progress, but not fully sorted.
1. This morning I uploaded a total of 1702 files via FTP, strictly in accordance with your instruction, that is to say the full folders and .php files you suggested. Immediately the site remained up, no more HTTP 500 and the original error that had been a lodger on my site for too long finally gone. To be replaced with this error UTC] PHP Strict Standards: Â Non-static method identify::get_ip() should not be called statically in /home/XXXX/public_html/modules/Forums/common.php on line 235 So I compared my current common.php with the one in your latest version, they differed enough (the -> again) for me to decide to just swap them out.Success, this new error gone.
2. Things remained stable until I logged in as Admin on the site, my admin screen blank with 2 entries in the PHP error log telling me
PHP Strict Standards: Â Non-static method identify::identify_agent() should not be called statically in /home/xxxx/public_html/blocks/block-CZUser-Info.php on line 262
and
PHP Fatal error: Â Using $this when not in object context in /home/xxxx/public_html/includes/classes/class.identify.php on line 195
I swapped out the block-CZUser-Info.php as it looked like another case of :: instead of -> in the $user_agent = $identify->identify_agent();
I did nothing with the class.identify.php, because that has just been added. The PHP error log cleared again.
3. I then tried to use Quick navigation to Admin(Nuke-Evo) I now get a white screen with ....
Uncaught Exception Has Occurred! Message: An error occurred while attempting to run a query on the database!
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 's Server Bans'' at line 1
File: /home/xxxx/public_html/includes/db/mysql.php
Line: 251
Stack Trace:
#5{main}
#4/home/xxxx/public_html/admin.php(368): adminMain()
#3/home/xxxx/public_html/admin/modules/index.php(65): GraphicAdmin()
#2/home/xxxx/public_html/admin/functions.php(481): is_mod_admin('~l~xxxx Serve...')
#1/home/xxxx/public_html/includes/functions_evo.php(108): sql_db->sql_ufetchrow('SELECT admins F...', 2)
#0/home/xxxx/public_html/includes/db/mysql.php(743): sql_db->sql_query('SELECT admins F...', true) Â Â
I am not inclined to regress using backups, not yet at least, because I think this is getting closer to a full resolution. The site is otherwise running and accessible, to forum users, it's just sorting my Nuke Evo Admin status. I can access forum admin and blocks etc other areas. But the Nuke Evo screen is a dud. I don't want to jump in from here and start swapping more files or second guessing what this needs, until you have had a chance to review the above error, and can suggest what you would be doing next.
Thanks
Topic: [SOLVED] Error log lodger
Forum: Nuke Blocks / Modules Support Posted: Mon Sep 24, 2018 9:51 am Subject: Re: Error log lodger
— coRpSE wroteBut overall, Only things you need to upload is the folder includes, and maybe admin. Then the files you would want to upload from your root is the header.php, footer.php, mainfile.php, admin.php and index.php. So, ot make it more simple, just make a backup of your site, replace those files/folder(s).Your files aren't corrupt, just, they coding is either old, or poorly updated.
Holding off doing what you have suggested above as my hosts have had some network issues. It took my site down for several hours today. So I will give it a day or two to settle, in case things take a dive again when I am mid way through trying different files etc...it would add confusion I do not need.
I prepared all backups, and updated files/folders to upload, taking into account stuff I added recently such as Honeypot.
I will update this thread in the next few days to hopefully to give it closure. Someone else might have a similar issue one day?
Topic: [SOLVED] Error log lodger
Forum: Nuke Blocks / Modules Support Posted: Sun Sep 23, 2018 12:44 am Subject: Re: Error log lodger
I should probably have confirmed it for you in my post, but the HTTP 500 and errors was with all three edited files in place. I understood the need to use all three. I created a simple backup folder and upload folder to ensure uploads and any fixes went easily, I even ran it twice to be sure.
To convince myself I did not err, I repeated the 3 files test this morning..with the expected HTTP 500 result
PHP Parse error: Â syntax error, unexpected '->' (T_OBJECT_OPERATOR) in /home/xxxxx/public_html/header.php on line 147
I think where I misled you is that I copied and pasted the line 182 error in with my previous post, which is of course the error that is the root error, and so you would think he forgot to fix that, it was a call from before the test.
So to be more accurate it is now barking out this syntax error, unexpected '->' (T_OBJECT_OPERATOR) in /home/xxxxx/public_html/header.php on line 147
which is in fact one of the lines recently edited ( $user_agent = identify->identify_agent();)
To convince myself I did not err, I repeated the 3 files test this morning..with the expected HTTP 500 result
PHP Parse error: Â syntax error, unexpected '->' (T_OBJECT_OPERATOR) in /home/xxxxx/public_html/header.php on line 147
I think where I misled you is that I copied and pasted the line 182 error in with my previous post, which is of course the error that is the root error, and so you would think he forgot to fix that, it was a call from before the test.
So to be more accurate it is now barking out this syntax error, unexpected '->' (T_OBJECT_OPERATOR) in /home/xxxxx/public_html/header.php on line 147
which is in fact one of the lines recently edited ( $user_agent = identify->identify_agent();)
Topic: [SOLVED] Error log lodger
Forum: Nuke Blocks / Modules Support Posted: Sat Sep 22, 2018 10:31 am Subject: Re: Error log lodger
I tried that next step edit you suggested and not unexpected HTTP 500 this time with ....
PHP Warning: preg_replace_callback(): Requires argument 2, 'Array', to be a valid callback in /home/xxxxx/public_html/includes/classes/class.identify.php on line 182
PHP Parse error: syntax error, unexpected '->' (T_OBJECT_OPERATOR) in /home/c426886/public_html/header.php on line 147
So I think it best we halt the piecemeal edits. I could be one more edit away, or dozens? I will do a series of backups and then install again using the version you provide. I have created some blocks, modules and numerous forum icons and images, it should be simple enough to backup, install again and recover where needed at least I assume that is the best way to use proven files over corrupt?
Thanks for giving this some of your time.
PHP Warning: preg_replace_callback(): Requires argument 2, 'Array', to be a valid callback in /home/xxxxx/public_html/includes/classes/class.identify.php on line 182
PHP Parse error: syntax error, unexpected '->' (T_OBJECT_OPERATOR) in /home/c426886/public_html/header.php on line 147
So I think it best we halt the piecemeal edits. I could be one more edit away, or dozens? I will do a series of backups and then install again using the version you provide. I have created some blocks, modules and numerous forum icons and images, it should be simple enough to backup, install again and recover where needed at least I assume that is the best way to use proven files over corrupt?
Thanks for giving this some of your time.
Topic: [SOLVED] Error log lodger
Forum: Nuke Blocks / Modules Support Posted: Sat Sep 22, 2018 9:10 am Subject: Re: Error log lodger
Okay tried those, HTTP 500 error with ...
PHP Strict Standards: Non-static method identify::identify_agent() should not be called statically in /home/xxxxx/public_html/header.php on line 147
PHP Fatal error: Using $this when not in object context in /home/xxxxx/public_html/includes/classes/class.identify.php on line 189
Sorry I know this is a long winded way of seeking your help, but I don't make use of any voice or messenger apps these days. For my part I am more than happy to keep trying things you suggest in your own time, as I can recover quickly from failures there is no urgency. I am very grateful for your efforts. Ultimately I have lived this bug spamming my error log (I clear it weekly) for some time.
PHP Strict Standards: Non-static method identify::identify_agent() should not be called statically in /home/xxxxx/public_html/header.php on line 147
PHP Fatal error: Using $this when not in object context in /home/xxxxx/public_html/includes/classes/class.identify.php on line 189
Sorry I know this is a long winded way of seeking your help, but I don't make use of any voice or messenger apps these days. For my part I am more than happy to keep trying things you suggest in your own time, as I can recover quickly from failures there is no urgency. I am very grateful for your efforts. Ultimately I have lived this bug spamming my error log (I clear it weekly) for some time.
Topic: [SOLVED] Error log lodger
Forum: Nuke Blocks / Modules Support Posted: Sat Sep 22, 2018 7:38 am Subject: Re: Error log lodger
— coRpSE wroteOkay, can you open up your mainfile.php file and send me 5 lines before and after that line that was throwing out that error.
// Include the required files
@require_once(NUKE_DB_DIR.'db.php');
//$db->debug = true;
// Include Error Logger and identify class
@require_once(NUKE_CLASSES_DIR.'class.identify.php');
global $agent;
$agent = identify::identify_agent();
@require_once(NUKE_INCLUDE_DIR.'log.php');
if (ini_get('output_buffering') && !isset($agent['bot'])) {
ob_end_clean();
header('Content-Encoding: none');
}
Topic: [SOLVED] Error log lodger
Forum: Nuke Blocks / Modules Support Posted: Sat Sep 22, 2018 2:23 am Subject: Re: Error log lodger
— coRpSE wroteOkay, try this, make a backup of what you have now and download the attached file and give this a try. I just modified the one you sent with a pretty original function.
I don't have any backups of any older files. What is in situ has been running for a while now. I may have edited it in accordance with some online forum advice on an old support website (now closed), but I can't remember any specifics - I'm just guessing on that tbh.
I tried the file you prepared that gave an instant HTTP 500 error.
PHP Strict Standards: Â Non-static method identify::identify_agent() should not be called statically in /home/xxxxx/public_html/mainfile.php on line 181
PHP Fatal error: Â Using $this when not in object context in /home/xxxxx/public_html/includes/classes/class.identify.php on line 189
I considered taking a backup of my existing "includes" folder, replacing it with the latest folder and all contents. Then decided to wait and see if you think that might just open up another can of worms.php
