Coly010

Also, remember that placement of script tags seems to make a difference, as well as that some functions won't work until the html is fully loaded

Just taken a look at this, looks pretty sweet and it's definitely easy to pick up.

I always have a problem with event.preventDefault(). it doesnt like me, i have to use event.stopPropagation(); also for it to behave.

It actually deletes more than just the current directory, it deletes every sub directory and file. "So nice try"? I think that was a very successful try.. you actually ran the code without knowing what it did...

That was another error added into the mix then, it's not the original error.

i think his issue could be coming from his DB structure :   $q_ry = "UPDATE memberstats SET my_labor = my_labor + ".$wj['r_MANUALGAIN']." , my_intelligence = my_intelligence + ".$wj['r_INTELGAIN'].", my_endurance = my_endurance +".$wj['r_ENDURGAIN']." WHERE playerid = ".interval($wj['playerid']) "; mysql_query($q_ry) or die(mysql_error());   as his error is this: 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 '=* +* '200'************* WHERE playerid = '5'' at line 2 I'm going to throw it out there that there is a problem with one of the column names. :/ that's if that is the correct query that is throwing the error. as [MENTION=68644]spikereloaded[/MENTION] said, go through your file and add echo "test passed - NAME OF CRON <br />" , that way you will know which query is actually causing you a problem

From looking through your file I have a feeling it may be to do with you $withjob query thing. Your file is a mess, that's as well as I can explain what line it is whilst on my phone. I can't copy and paste it.

it doesn't. Inside joke, just ignore.

back-ticks ? ;)

the only way i think js could in anyway provide a responsive design is if you dynamically load a different stylesheet depending on if its mobile or not. bootstrap would be the preferable option in my opinion

Well if you split them up like that, then one benefit I can see (@IllegalPigeon correct me if I'm wrong) as there are less columns in the tables, if you only need to access the money, then querying a table that has 4 columns rather than 24 will be faster?

Yep :) [MENTION=71474]cmd[/MENTION] , if you are using mccodes i believe there is already a settings table, with conf_name and conf_value, rather than key_name and key_value, so the table is already set up. Just add the records to this table :)

I never said that because it was overkill it was going to under-perform. I can accept that I am wrong, I don't claim to know everything. But when you call me out, correcting me on something that you think I have said when I never said anything of the like. I never said my framework was better, I simply didn't need all the features of Laravel etc. So I made my own framework as a challenge to myself. If you read the post I said that some devs are ignorant of things that can actually help them? There was nothing incorrect in that post. I will admit I was wrong on the sessions. I posted based on what I believed to be correct. I know you think that you aren't attacking me, but it really does feel that way and I'm sorry if I reacted defensively but you would too if you feel are being harassed. Let's just leave it there ok? I make posts based on the info I know, not based on an expert inside out knowledge of everything dev related.   Trust me, I thank you for that. I did a ton of research on Sessions after that discussion. I can admit I'm wrong. I give out enough criticism to know how to deal with it in return. If I feel I'm right I happen to argue it out for a while until I get the time to do the research to find if I'm wrong. If I find I am wrong I admit it.

You are really starting to piss me off. You seem to have something against me and what I do. I never said it would compete with Laravel, I never said it would be faster than Laravel. I stated that it was an extremely basic framework. Not once did I say it was in anyway better. I simply said that Laravel had a lot of features I didn't need. I never said that I wanted my own framework because it would give me any more benefit than Laravel would. If you read the topic I created on ChaoticFrame, I said about how it was a challenge to myself to be able to set it up and create it. I never said it would give anyone any benefits over any other framework. I HAVE NEVER CLAIMED TO BE AN EXPERT DEVELOPER, I DO NOT KNOW EVERYTHING ABOUT EVERY LANGUAGE AND FRAMEWORK. There you happy [MENTION=71663]IllegalPigeon[/MENTION] ?

LOL! That's devs being ignorant. There are some devs that feel like you just do everything yourself and other devs which feel you should use things that make your life easier. I've worked with CodeIgniter and decided that I didn't want to use it or Laravel for my current project as it is overkill. There's too much there that aren't needed or won't be needed, so I set up a very very basic framework for my project. VERY BASIC, as it doesn't use namespacing etc. It should, but the framework is still being developed. You can make your own, but good luck. You need to learn a ****e ton about http, routing, etc The first four points are OOP, not framework. You'll learn, you don't just learn OOP overnight. It's what I call progressive learning. After learning the basics, As you use it, you learn more. As you see code examples using it, you learn more. Etc

Not neccesarialy just php. And as [MENTION=71587]~Rob0t[/MENTION] said, learn one inside out. However, Id also say to familiarise yourself with the rest as you are currently working freelance and a client could request you use a certain framework and it's not the one you know best. So familiarise yourself with the popular ones but pick one of them and become a guru in it :p guru is a bit much, but just really learn it. Also most frameworks use OOP. So learn it.

I never said that him storing his data in the session would take up all his memory, I just said it would use it, as from what was previous my understanding was that assigning a value to a variable uses memory. And it was my understanding that $_SESSION was a global variable and hence it would use memory. Also, memory does get used, so I'm still correct in thinking that it would use memory, it just doesn't use enough to crash the server? Yes you are right about not having to worry about memory, but by going down that the route of storing and reading data from sessions you will use memory. I will admit I stand corrected because what I had believed was wrong. I always knew that sessions where written in files. Also, it the answer I got from Google doesnt "completely" agree with you. Did you miss out the part that said it uses memory when reading the data? No, you didn't you just ignored it because you focused solely on the storing of data, whereas I was looking at the bigger picture. You wouldn't store data in a session if you don't intend to read it again. Anyway, thats my last post on the subject. I stand somewhat corrected.

So, what you are saying to me is that if I have 1GB RAM on a server and i try to execute this code: ob_start(); for($_SESSION['iterator'] = 0; $_SESSION['iterator'] < 3000000000; $_SESSION['iterator']++;){ echo $_SESSION['iterator']."\r\n"; } ob_end_flush();   it'll run completely? just gonna drop this answer here also... http://stackoverflow.com/a/17558888 its not about writing the session, its about reading from it. I know that you probably think that i've linked an answer that agrees with what you were saying. It has in a sense, but in another it has agreed with me. When writing the Session Data it gets stored on disk space, when reading the data again, memory gets used. As this is a game and the session read from a lot it is going to use memory.

[MENTION=64684]Dayo[/MENTION] [MENTION=68711]KyleMassacre[/MENTION] [MENTION=69823]jcvenom[/MENTION], learn frameworks. PHP : Symfony, Laravel, CodeIgniter JavaScript : Angular.JS , Node.JS, Express.JS, Socket.IO Learn CSS Precompilers : LESS, SASS

Not exactly. Every variable you set uses memory. So the more data you store in the $_SESSION (which is a global variable) the more memory you will use.

It's because of how the application is set up, I know that if an int is 0 then if(int) would return false.

Thank you! Needed this posted I think haha. Node.js itself is pure javascript is it not? And that is run backend, anything you build using node.js is using the node.js library , not exactly pure javascript, but node itself is. I know from the OP perspective he meant front-end, I just think it's best to clear up that javascript is not purely front end. [MENTION=64603]Sim[/MENTION] I think we would be a_bertrand to clear this up for us lol

[MENTION=69670]Script47[/MENTION] you can't tie javascript to either front end or backend. It's more universal than that. When used in front end its tied to the DOM, when it's used backend it isn't. It's not specifically a web language either.

Not necessarily... Node.js ... It uses JavaScript, it is backend. I have even seen JavaScript outside the browser... Unity Game Engine

I was indeed on the same track as Kyle. Talking PHP wise, if you want to store them in $_SESSION, be my guest, it'll take up memory though. Your page will most likely make calls to select something from the database relating to users table, so i dont feel the need when i can just include those fields that appear often. If you were storing only static values in $_SESSION, thats a different matter. Values that arent going to change. their userid, username, email etc. but i wouldnt store fields that are changing. as for storing it in cache, what happens if someone deletes their browser cache?