Philip
Staff Alumni-
Posts
4,665 -
Joined
-
Last visited
-
Days Won
20
Everything posted by Philip
-
Welcome to phpfreaks Brad!
-
Ah, like a WYSIWYG editor
-
Given that you've been using bold and a quote tag in your signature all along, I'd say yes you can use some bbcodes there
-
I thought this was already in place with the core files? Or are we getting what the "profile page" is mixed up?
-
To be fair, with that example - the CSS file size will increase. With SASS/LESS it basically adds in those properties (last time I checked), so instead of // css .center { margin: 0 auto; } .big { font-size: 120%; } .normal { font-size: 100%; } .small { font-size: 80%; } // html <div class="center big">...</div> <div class="center small">..</div> You'll have this: // css .big { font-size: 120%; margin: 0 auto; } .normal { font-size: 100%; margin: 0 auto; } .small { font-size: 80%; margin: 0 auto; } // html <div class="big">...</div> <div class="small">..</div> So the only time it really reduces it is if you have many calls to the same style choices. The way to save file size/bandwidth in this case would be to combine them: // css .big, .normal, .small { margin: 0 auto; } .big { font-size: 120%; } .normal { font-size: 100%; } .small { font-size: 80%; } // html <div class="big">...</div> <div class="small">..</div> However, IMO the whole point of the using ".center .big" is to allow for the HTML to be more versatile during redesigns, which is why I'll continue to stick with it - especially for things like rounded edges / shadows.
-
Since you're not using them (in our view) for anything else you could just do this: <?php if (isset($_POST['likes'])) $array[] = $_POST['likes']; if (isset($_POST['dislikes'])) $array[] = $_POST['dislikes']; if (isset($_POST['hidden_con_id'])) { $array[] = $_POST['hidden_con_id']; //$favorite = $_POST['favorite']; } Or do something like this if you need to use $likes later: <?php if (isset($_POST['likes'])) { $likes = $_POST['likes']; $array[] = $likes; }
-
Let's all cool down guys. If the topic is solved, let's mark it as so, if not let's stay on topic and not be bickering to each other.
-
You'd better hurry on finding a new developer! Looks like you only have 1 day, 8 hours left until launch!
-
Make sure to have the following since you're using subdomains: _gaq.push(['_setDomainName', '.mysite.com']); And I'd change the web properties to the highest domains (in this case http://mysite.com) There are several tools to debug - GA has a Chrome Extension. My favorite (and what I use daily) is Firebug + Omnibug for Firefox.
-
Man, if that's how you felt, I'm pretty sure I would have demoted myself the first day on the job
-
It really depends on your needs. The other frameworks (read: CI, Yii, Symfony) may not have been around as long as ZF, but I think they are definite contenders.
-
Yup, both SASS and LESS are awesome tools to use when creating CSS. They make development time a lot quicker - however do note that the output of the CSS is nowhere near as clean as if you were to do it yourself.
-
And all of your docs are TLDR's
-
Ugh, if only that would happen...
-
Yeah, Chili's has a few bugs that I've ran across too... I've also had an order from Domnio's pizza when they first launched their online order system and it had the options pepperoni on the full pizza or half pizza. When I got the pizza it was a cheese pizza because apparently between the online ordering system (which sent me an email confirming pepperoni all the way across) and the kitchen there was a bug because the order they received said "no pepperoni". Morale of the story: test, test, test!
-
Online IMO is: More cost effective for the employer: Employees can multi-task between taking orders online if they are even required because it can be completely automated into the kitchen Less food waste from mis-understood orders because now the user orders it all themselves and is directly printed on the kitchen order [*]Better customer experience: satisfaction of knowing exactly what you ordered and what would go in the kitchen The list could go on, but ordering online is a lot more enjoyable for me. However, some people still like to talk to a real person when spending $$.
-
how much data can you safely store in the url?
Philip replied to dadamssg87's topic in Application Design
Real world limit is roughly 2,000 characters. Your URLs called are going to be logged in an access log (if you're using apache) -
Good explanation kicken, just a quick side note, However, do note that src objects (such as for image tags, script tags, style tags, etc.) will need to include the correct protocol when you're using an absolute URL. You can get around this by prefixing your URL with // instead of http:// or https:// as seen below: <script src="//domain.com/file.foo">
-
... there are 4 pages on the coding standards.
-
I tend to follow Zend's coding standards for most things, mainly because the file name is associated with the class name
-
I'd suggest looking into the design pattern MVC This will help you separate your code from your html. Working with a framework can help you stick to a design pattern (such as MVC)
-
Don't get the web accessable root mixed up with the filesystem root. Just because you name a constant "root" doesn't mean it is the same thing as the root directory. In this case, with your constant ROOT the following are the same when in a development env: <?php // Defining your root define('ROOT', '/Users/user1/Documents/DEV/++htdocs/03_MySite/'); // These are the same: require ROOT . 'file.php'; // as this: require '/Users/user1/Documents/DEV/++htdocs/03_MySite/file.php'; // The following will not, because it will look for C:\file.php instead of C:\Users\user1\Documents\DEV\++htdocs\03_MySite\file.php require '/file.php'; Using your example: <?php require_once(ROOT . 'components/body_header.inc.php'); // Requests the file C:\file.php instead of C:\Users\user1\Documents\DEV\++htdocs\03_MySite\components\body_header.inc.php // whereas... require_once('/components/body_header.inc.php'); // Requests the file C:\components\body_header.inc.php See the difference? Now, the ../ means "go to parent directory", as mentioned before. Actually, you can just read all about it here. No need for me to retell what has been told