falkencreative

Not really, unfortunately. Are there any areas you think are too low contrast?

@eddie - There is a "View Unread Posts" option (main navigation, top right). That gives you options for viewing posts you haven't seen yet, with time-based limitations so you can look at the last 24 hours, week, etc. Does that do what you want?

I've updated the forum to use the usual KillerSites greens rather than the forum's default blue themes. However, this is a relatively big piece of software with a lot of functionality, so if there's anything I missed, please reply or send me a PM so I can fix it. Thanks!

I tried emailing you back, but I always got an error when trying to email your email address unfortunately. As for your question, I imagine it's not technically something that is wrong with the syntax, but that $items is either null or empty and the query doesn't know how to handle that (since that isn't an expected value). The first step would be do figure out what $items contains within the get() method when the error occurs, and then work back from there. I'd likely have to step through the entire logic of the page request to see how $items is set in order to resolve it. I'll see if I can take a look near the end of the week.

At least for me, I use a Mac in my videos because that's what I have, and that's the platform that supports the text editor that I use. I'm a designer, and like a lot of designers, I use a Mac. At least for my videos (PHP primarily), the code I use should work and display fine no matter what platform the viewer uses. Which video course are you watching specifically? And what differences are you seeing?

Your files should be up now. Sorry -- I just never check that section, and I don't get alerts when files get added.

As a screencast author for Killersites, I'll repeat:

Maybe you should ask Lynda.com support then? We have nothing to do with Lynda, so I imagine asking them directly will get you better results.

Well, at least at KillerSites, we are conspiracy theory free. Stefan has made no requests regarding how we phrase what we call the tutorials. As a screencast author, I tend to call them "tutorials" or "videos", but not usually "movies" (perhaps I'd call a extremely long, non-stop video a movie, but in my mind, a movie is an hour+ long, so my 10 minute videos don't count). It sounds like the author of the Photoshop course called them "movies". How we refer to them depends on our preference. Copy protection is built into anything you post online -- it doesn't matter whether one calls it a movie or tutorial or video or whatever. This has a reasonably clear explanation of online copyright: http://www.socialmediaexaminer.com/copyright-fair-use-and-how-it-works-for-online-images/

Sure, "lesson" or "tutorial" would make more sense. "Movie" or "video" still gets the point across. Most lessons are recorded with a rough outline in mind, but no script, so there will be times when someone is bound to say something that isn't 100% perfect. If it doesn't change the understanding of the concept, it usually isn't worth it to potentially re-record the entire video for something very minor. I guess I don't see what the big deal is? The point is that you're learning whatever subject you are studying, not a minor word choice.

I've been using https://interconnectit.com/products/search-and-replace-for-wordpress-databases/ (version 2) to update paths in the database. You can enter the old and new paths, and the script will automatically find/replace. I've found it pretty useful when moving a site over between the development site and the live hosting. Hope that helps?

This is a pretty useful interactive tutorial that guides you through working with Git: http://try.github.io/ You should be writing commands in the terminal. Unless that's not what you are asking?

Right. RGB is for web/screen work, and CMYK is for print. They have different color gamuts (meaning the range of colors they can display), and CMYK specifically has a smaller range of colors it can create from the cyan/magenta/yellow/black combination of inks. This is often why you'll see colors shift slightly when switching between the two, because the calculations used to create those colors from the combinations of inks change.

Yes, if you are doing print work, you need to be working in CMYK, which is what the item will be printed in. Otherwise, yes, it will get automatically converted to CMYK, and you might get unexpected results.

A "cannot modify header information" error means that you are sending data to the browser before trying to redirect using header(). I'm not sure exactly what your code looks like, but make sure you aren't echoing anything out before calling header(), and that there aren't any stray spaces at the start of the file before the opening PHP tag.

I was going to respond to your email, but doing it here makes more sense in case others run into the same thing. the get_sidebar() function loads a sidebar.php file within your theme. Get_sidebar() loads sidebar.php, get_sidebar('sidebar-2') would load sidebar-2.php, etc. So if you want to use those functions, you have to make sure that the correct files are in place. Within your sidebar.php/sidebar-2.php, you'd want to have the dynamic_sidebar() call to load the correct sidebar. It's a bit hard to tell based on your code, but I think you have a file named "sidebar2.php", when it should be named "sidebar-2.php" (note the dash). http://codex.wordpress.org/Function_Reference/get_sidebar http://codex.wordpress.org/Function_Reference/dynamic_sidebar

I'd suggest emailing Stefan directly -- he should be able to help you. stefan [at] killersites.com

Sorry, you're going to have to rephrase the question, since I'm not sure what you are asking. But my original point still stands. A CMS is a web application. A framework is a pre-built structure that you can use to build web applications quicker/easier than starting from scratch. Think of it this way: a CMS is a fully built house. A framework is the plans for the house.

Sorry, I'm not super familiar with Joomla -- you'll have to do some research on that.

They are different things. -- A CMS is a web application for content management -- usually to do with an informational website, ecommerce store or blog, allowing a user to edit the content without needing to know HTML/CSS or to code by hand. -- A PHP framework is used to build web applications, quicker and easier than by starting from scratch. You could use a PHP Framework to build a CMS, an ecommerce platform, a social networking platform, etc. Basically, a CMS is a web application, and a framework can be used to build web applications. For example, Expression Engine CMS is built on a version of the CodeIgniter framework.

What's confusing about the chart? It shows the actions handled by the controller, describing the server method used (GET, POST, DELETE), the path used, the primary action when that path is accessed, and the route name. It is there to help describe the functionality that you will be building. As for CSS, take a look at http://www.tannerhearne.com/link-to-css-file-laravel-using-html-class/. You can also hard-code the link to the CSS file, like the link to the Boostrap CSS file in http://scotch.io/tutorials/simple-laravel-crud-with-resource-controllers. CSS files should go in the "public" folder -- either directly in that folder, or within a subfolder within the "public" folder.

If I can offer a suggestion to you though... -- If you are going to be reading the user manual, and assuming you have access to the internet, I'd suggest you be reading the official docs instead: http://laravel.com/docs.'>http://laravel.com/docs. What you are reading now is a version of the documentation (last updated mid last year), copied and pasted, but at least if you go to http://laravel.com/docs you know you'll be reading the most up to date information. I wouldn't suggest reading a PDF version unless you are on the go and don't have internet access. -- Secondly, I'd suggest you skip the official documentation for now, and find a relatively simple introductory tutorial to Laravel that will give you an idea of the overall structure and how things work together before reading the documentation. There's likely to be a lot of things in the documentation that you won't use very often and will just add unnecessary complexity and confusion. Perhaps start with a "getting started" type tutorial, and come back to the full documentation when you are a little more familiar with the way it works? You might consider something like this: http://scotch.io/tutorials/simple-laravel-crud-with-resource-controllers which will give you an overview of a lot of common functionality: working with routes, models, controllers, views, the database, etc.

Filters allow you to run code either before or after a route (so yes, you can have both "before" and "after". Before tends to be useful if you need to do some sort of authentication checking or validation -- perhaps you want to make sure a user is logged in before they view that particular page. "After" might be used for code cleanup -- it's likely something that you won't use. In the code above, it is calling the "old" filter before the route runs. The get('age') section refers to a GET variable in the URL, so try accessing the site using something like this: yoururl.com/user/?age=50 (should redirect) or yoururl.com/user/?age=201 (shouldn't redirect) I believe that should work, since age is set.

As far as I understand it, that code allows you to automatically determine where the site is running, and what environment it is running in. For example, you may be running it in several places -- perhaps locally on your computer, on a hosted development site, or live online for anyone to view -- an in each case, you're likely to have a different database setup, and perhaps certain code (logging, for example) would run only under your development environment. The environment variable allows automatic switching between environments based on the host name, and you can then use App::environment() to determine which environment you're running under and thus perform specific actions. See http://laravel.com/docs/configuration#environment-configuration for more, or do a Google search for "laravel environment".

No, that isn't something you'd do using functions in Laravel. In Laravel, you'd use the blade templating functionality -- "sections" specifically. Learn more: http://laravel.com/docs/templates http://culttt.com/2013/09/02/using-blade-laravel-4/ http://scotch.io/tutorials/simple-laravel-layouts-using-blade