Copy Paste Coder @copypastecoder-blog - Tumblr Blog

FuelPHP querying ObjectID or _id from mongoDB

To query documents by ObjectID, you can't just pass in a string, you need to send in PHP's Object/Type MongoID

public function action_getstuff() { $mongodb= \Mongo_Db::instance('default'); $userID1 = '4f98c2f6f26c618f21000002'; $userID2 = '4f976a38f26c619121000002'; $result = $mongodb->where_in('_id', array($userID1, $userID2))->get('Users'); if($result) { echo "got Results with userID strings"; } $result = null; $mongoID1 = new MongoID($userID1); $mongoID2 = new MongoID($userID2); $result = $mongodb->where_in('_id', array($mongoID1, $mongoID2))->get('Users'); if($result) { echo "got Results with MongoID objects"; } }

You should get results on the 2nd query with the MongoID objects. If you are in your Model, and using a namespace, remember to reference the MongoID object with \MongoID

#FuelPHP #mongoDB #ObjectID #_id

FuelPHP updating embedded array documents in mongoDB

For some reason this was a DOOZY of problem. And it's because i didn't thoroughly read MongoDB's documentation!!!! They have it right there... The $ Positional operator is your friend! You should read mongodb's documentation page. But since you're already here, let's take a look at a very simple example using FuelPHP. Let's assume your schema looks like this. You are tracking anytime somebody clicks on a users links in their profile.

{ username:"jim", email:"[email protected]", links: [ {url:"http://www.73ro.com", visits:0}, {url:"http://flavors.me/jimmers", visits:3} ] }

I like to query the data first, to make sure we have a row to update. I don't use an upsert here, because the mongoDB documentation (yea, i read that in there this time) states that if it does not exist, it will insert a field name containing the '$' sign.

//Somehwere in our controller we have a function like this ... public static function click_link($url) { $mongodb = \Mongo_Db::instance('default'); $result = $mongodb->where(array('username'=>"jim", 'links.url'=>$url))->get_one('Links'); if($result) { $mongodb->where(array('username'=>"jim", 'links.url'=>$url]))->update('Links', array('$inc'=> array('links.$.count'=> 1)), array(), true); } }

the first lines should be familiar to you. Choosing the instance, then finding a row in the DB. The thing that might seem strange is the "links.url" part. Well you can use the dot notation to dig deeper into embedded objects. So I could go as deep as i needed if I had to (comments.author.firstname...) if i had to go deeper. the tricky noise, and what was causing me headache, was when you do an update, you can't just use the dot notation. You have to throw a dollar sign in between, so i did 'links.$.count', then it knew in the scope of this document where to update the count. This was a basic instruction, if you don't understand it read over the documentation at mongoDB. If it's still eluding you feel free to message me, i'd be glad to help, as it caused me a night of frustration. I finally found the mongodb google groups and it lead me to the solution. Great place, check it out if you haven't

#FuelPHP #mvc #mongoDB #embeddedArray #nosql

How to use $inc in FuelPHP with mongoDB

So if you want to use $inc with fuelphp and mongodb, or any of the other update commands besides $set ( which is the default) it is possible. It's undocumented however unless you look into the code. Again here is our controller code

Class Controller_About extends Controller { public function action_index() { $data = array(); $data['name'] = "CopyPasteCoder"; $data['age'] = 27; //echo "This is my first attempts at MVC architecture."; return View::forge('about', $data); } public function action_water() { $result = Model\About::get_count(); echo "i'm thirsty $result"; } public function action_supMe($name = '') { $data = array(); $data['name'] = $name; $data['age'] = 27; return View::forge('about', $data); } }

And our model looks like this

namespace Model; class About extends \Model { public static function get_count() { $mongodb = \Mongo_Db::instance('default'); $result = $mongodb->where(array("name"=>'about'))->get('counter'); $count = $result[0]['count']; return $count; } }

let's modify the get_count() function to actually increment the count in 2 ways.

public static function get_count() { $mongodb = \Mongo_Db::instance('default'); //increment the old fashion way, get row then increment $result = $mongodb->get('counter'); $count = $result[0]['count'] + 1; $mongodb->where(array('name'=> 'about'))->update('counter', array('count'=> $count) ) ; //using increment functionality ($inc) $mongodb->where(array('name'=>'about'))->update('counter', array('$inc' => array('count'=>1)), array(), true); return $count; }

the first way is the classic way of incrementing. Get counter, increment, update with set. The second way is calling update with an extra hidden field. So the function definition for update is public function update($collection = '', $data = array(), $options = array(), $literal = false) What we want to do in JSON is db.counter.update({"name":"about"}, {$inc : {"count" : 1}}) So lets break it down where(array('name'=>'about')) = {"name":"about"} array('$inc' => array('count'=>1)) = {$inc : {"count" : 1}} Then i pass in a blank array(), because i don't have any options Then i pass in a true so $literal = true. THIS is what allows us to use $inc, otherwise it defaults to $set.

#$inc #FuelPHP #mongoDB #update #MVC

FuelPHP finally getting data from mongoDB into our model

So we have a model, but it's not getting anything from the database. Let's get that counter from our mongoDB. Again here is our controller code

And our model looks like this

namespace Model; class About extends \Model { public static function get_count() { $count = 56; //Will get this from the DB SOON. return $count; } }

Now let's modify our model to get data from the DB with this code.

The first line instantiates our mongoDB object that we will use to run queries. Note the capitalization on Mongo_Db and the namespace '\'. We get the default instance, as defined in our config/db.php file. The next line we store our queried data into an array called $result. When calling the mongodb object, you can specify a where clause before the get. Then because MongoDB uses JSON to query data, we need to send in arrays. this is pretty much doing db.counter.find({"name":"main"}) The result set is an array, and i only expect 1 row. So i just pull the count column from the first row. then i return this data. That's it, it should be pulling back 1!

#FuelPHP #mongoDB #MVC

FuelPHP creating our first model

So at this point, you already have a view, and a controller, but aren't using any models yet. Let's make a simple model for our controller to call. Again here is our controller code

Class Controller_About extends Controller { public function action_index() { $data = array(); $data['name'] = "CopyPasteCoder"; $data['age'] = 27; //echo "This is my first attempts at MVC architecture."; return View::forge('about', $data); } public function action_water() { echo "i'm thirsty"; } public function action_supMe($name = '') { $data = array(); $data['name'] = $name; $data['age'] = 27; return View::forge('about', $data); } }

Now go to /fuelphp/fuel/apps/classes/model/ and create about.php then drop this code in there

namespace Model; class About extends \Model { public static function get_count() { $count = 56; //Will get this from the DB SOON. return $count; } }

At the time of me writing this, i don't know why we have to use the namespace Model and extend using \Model. I understand that if we are in namespace Model we do the \Model to retrieve the Model class that is outside of our namespace. But why do I have to use namespace Model in the first place. Why can't i just extend Model, the way controller does? I tried changing the namespaces, but it never seems to work.Update below! But to get data back from the model, let's just edit our water function above, and get some data back.

public function action_water() { $result = Model\About::get_count(); echo "i'm thirsty $result"; }

Just like that we got data back from our Model, pretty easy. One thing, we could do is at the top of our controller file is add use \Model\About;. This lets our controller know about the About model, and let's us reference it like About::get_count();

So we made a call to our model to get back some data; "big deal, I could have just done it in the Controller" You could have, but with separate functions and a separate class, it will make things a little cleaner. It separates duties. So the model can get the data, clean it up. The Controller can take the data, analyze it, then decide what to display. Then the controller can send it to a view for consumption. It is much cleaner than all of this happening in one function. Again can somebody can explain the reason I can't use other namespaces for Model (if i figure it out i'll make a post and let erryone know)? **UPDATE: I went over to the Forums at FuelPHP, and a bright guy by the name of WanWizard explained it all.

Basically its all about filename resolution using the class/namespaces. so I could use class Model_About extends Model {...} and call it using \Model_About::get() from the controller or use namespace Model; class About extends \Model{...} and call it using Model\About::get() from the controller and in both cases it would call /fuel/app/classes/models/about.php And in my above example if i created a directory /fuel/app/classes/models i could put my about.php in there. And use namespace Models if i wanted.

#FuelPHP #MVC

FuelPHP, setting up your mongoDB

We want to create a database now to insert data into. Most people go with the blog concept, and I will do the same for now. But this is only going to be a very basic setup. We are just gonna create the DB and a collection for us to use.

Pop into your terminal/shell program or RockMongo. However you can manually insert some data our MongoDB server. I'm gonna assume you are using the shell here and use shell commands.

>sudo mongo >use blog >db.counter.insert({"name":"about", "count": 1}) >db.counter.find()

What we just did was go into out mongo terminal, changed our working db to blog, and inserted a collection called counter, with a record Name=Main, and Count=1.

Note the JSON syntax. (if you don't know JSON, you gotta learn that to use mongoDB.)

until we insert something into our database, it isn't saved. Thats why we manually did it.

Note the 1 after "count": has no quotes. **Important. This way its saved as an int, instead of string

db.counter.find() just lists all the rows

now in our /fuelphp/fuel/app/config/db.php we have already modified it and setup our connection like the following.

'mongo' => array( 'default' => array( 'hostname' => '192.168.2.7', 'database' => 'blog', ), ),

You guys with me so far?

#FuelPHP #MVC

The phpmyadmin for mongoDB

If you are looking for an administrative web GUI for mongoDB, i recommend using RockMongo. It has a familiar layout to phpMyAdmin, and is also very clean. It looks like you can administer multiple servers as well. It's painless to install, just drop it in and modify the config.php. There is another option, phpmoadmin, but the UI could use some work. It's nice because its fast and its 1 file to just drop in, but again the UI isn't as obvious, or powerful ( from first looks)

#FuelPHP #mongoDB #rockmongo #phpmoadmin

FuelPHP, how to move your public directory

You may have asked the question, How do I move my fuelphp public directory? It's easy, it's all in the /fuelphp/fuel/public/index.php First decide where you want to put it, i chose up one level, so then I wouldn't have to type public anymore. So now i could access my site at http://192.168.2.7/fuel/ instead of http://192.168.2.7/fuel/public So move /fuelphp/fuel/public/index.php up one level, and then open it to edit it. and look around line 13 for stuff that looks like this

... /** * Path to the application directory. */ define('APPPATH', realpath(__DIR__.'/fuel/app/').DIRECTORY_SEPARATOR); /** * Path to the default packages directory. */ define('PKGPATH', realpath(__DIR__.'/fuel/packages/').DIRECTORY_SEPARATOR); /** * The path to the framework core. */ define('COREPATH', realpath(__DIR__.'/fuel/core/').DIRECTORY_SEPARATOR); ...

Notice how I have modified the PATH definitions to remove the relative path going up one level. If you aren't sure what relative paths are, i'll just give a quick example of what happened. __DIR__ prints out the current directory /fuelphp/fuel/public/ using ../ takes us up one level to /fuelphp/fuel/ then the /fuel/core/ takes us to /fuelphp/fuel/fuel/app/

If you still don't understand, read up on relative paths. Or shoot me a message.

#FuelPHP #MVC

FuelPHP setting up your mongoDB connection

So when I was first connecting to my mongoDB, I set it up this way

'mongo' => array( 'default' => array( 'hostname' => '192.168.2.7', 'database' => 'blog',), ),

This resulted in this error Fuel\Core\Mongo_DbException [ Error ]: Unable to connect to MongoDB: Operation now in progress That was the address of my local dev server, where the mongoDB was hosted, as well as my LAMP server. turns out what I needed to do was changed it to use localhost

'mongo' => array( 'default' => array( 'hostname' => 'localhost', 'database' => 'blog',), ),

it worked easily after that. But if you want to have it set to an ip, let's say your DB server is another server. In that case you gotta edit this file in your mongodb configuration. sudo nano /etc/mongodb.conf look for the bind_ip = 127.0.0.1 This means it will only allow connections from localhost. So in my case I changed it tobind_ip =192.168.2.7. But this only allows connections on that one IP. So if i comment out that line #bind_ip =127.0.0.1 then it will allow connections from anywhere. Commenting it out is equivalent to setting it bind_ip = 0.0.0.0 If you don't have a database setup yet, we can set that up later, but you can put that there for now.

#FuelPHP #MVC

FuelPHP some basic routing

Before I jump into models, lets have a little fun with routing. Right now if you been following along, we got a view

<h1>About</h1> <hr> <p><blockquote>Created using FuelPHP. An experiment into the MVC architecture</blockquote></p> <br><?php echo $name ?> <br><?php echo $age ?>

and controller

Class Controller_About extends Controller { public function action_index() { $data = array(); $data['name'] = "CopyPasteCoder"; $data['age'] = 27; //echo "This is my first attempts at MVC architecture."; return View::forge('about', $data); } public function action_water() { echo "i'm thirsty"; } public function action_supMe($name = '') { $data = array(); $data['name'] = $name; $data['age'] = 27; return View::forge('about', $data); } }

Lets take a look at routing. Pop open /fuelphp/fuel/app/config/routes.php it should look something like this

<?php return array( '_root_' => 'main', // The default route '_404_' => 'welcome/404', // The main 404 route 'funky' => 'about', 'funky/(:any)' => 'about/$1', 'hello(/:name)?' => array('welcome/hello', 'name' => 'hello'), );

Notice the 2 lines with funky in them. I have added a route, so anytime you want to access ...index.php/about you can type in ...index.php/funky and it will take you to the same place.

Note I had to add 2 routes. The main one 'funky => 'about' routes the main action_index()

The next one 'funky/(:any)' => 'about/$1' routes any other functions, like action_water, and action_supMe($name)...

Call supme with a name, see it work!

So we re-routed the user to the same pages using a router "mehh, I could have just called it funky if I wanted" I haven't thought of any good reason for routing yet, but i'm thinking if you have to move directories of files, or maybe if you had some kind of clustered setup. I'm not sure yet, but it's some powerful stuff. Does anybody have a good example of routing they can tell me?

#FuelPHP #MVC

FuelPHP sending data from the URL to a view

Let's modify the view to output some data from the controller passed in from the parameter string

<h1>About</h1> <hr> <p><blockquote>Created using FuelPHP. An experiment into the MVC architecture</blockquote></p> <br><?php echo $name ?> <br><?php echo $age ?>

note the php short hand, you don't need the semicolon (but it's only 1 more character, so to each their own. If you try to pull this up you won't get anything of value. Let's modify the controller to send in this data now.

Class Controller_About extends Controller { public function action_index() { $data = array(); $data['name'] = "CopyPasteCoder"; $data['age'] = 27; //echo "This is my first attempts at MVC architecture."; return View::forge('about', $data); } public function action_water() { echo "i'm thirsty"; } public function action_supMe($name = '') { $data = array(); $data['name'] = $name; $data['age'] = 27; return View::forge('about', $data); } }

I modified our supMe function. So now the name passed into the URL string, will get pushed out to our view. So pull up the site at ...index.php/about/supMe/Carlos you should see the name passed in from the URL. You could make your own view for the SupMe function now. Try that on your own. Remember to let the View::forge() know about the name of your view. And you can send in data or not if you want.

So we passed in variables from our controller and they got extracted to their key names "ok, that is pretty cool" yea. it is. (copy paste bro)

#FuelPHP #MVC

FuelPHP, sending data into a view

Let's modify the view to output some data from the controller. Let's say its name and age. So modify the view in /fuelphp/fuel/app/views/about.php to contain the following

<h1>About</h1> <hr> <p><blockquote>Created using FuelPHP. An experiment into the MVC architecture</blockquote></p> <br><?php echo $name ?> <br><?php echo $age ?>

Class Controller_About extends Controller { public function action_index() { $data = array(); $data['name'] = "CopyPasteCoder"; $data['age'] = 27; //echo "This is my first attempts at MVC architecture."; return View::forge('about', $data); } public function action_water() { echo "i'm thirsty"; } public function action_supMe($name = '') { echo "hey whats up $name!"; } }

See all i did was make a new array called $data, then i assigned it 2 values under the key's name & age. Then in my return i passed in the array. When you call the view::forge, it does an extract, and all the elements in our data array, become their key name. So thats why in the view we can use echo $name. $data['name'] turned into $name.

the name of the array you pass in doesn't matter.

it could be $data, $stuffs or whatever you want, as long as it's not a reserved array like a get or post array.

When you pass in data to a view, it is automatically encoded. Try changing the name to Joe

instead of being bold, it shows the tags, cuz it converted them to & g t ;

So we passed in variables from our controller and they got extracted to their key names "ok, that is pretty cool" yea. it is.

#FuelPHP #MVC

FuelPHP, making the first view

So if you have been following me so far, I just been using controllers with FuelPHP. I'm gonna show how to easily implement a view. Let's revisit our Controller.

Class Controller_About extends Controller { public function action_index() { //echo "This is my first attempts at MVC architecture."; return View::forge('about'); } public function action_water() { echo "i'm thirsty"; } public function action_supMe($name = '') { echo "hey whats up $name!"; } }

Note, in the action_index() function, i commented out the echo. Then i added some return nonsense. I call the View class, forge function to retrieve the view 'about'. If you try to pull up the index page, nothing will come back since we haven't created the view. Let's create the view /fuelphp/fuel/app/views/about.php And put the following in it.

<h1>About</h1> <hr> <p><blockquote>Created using FuelPHP. An experiment into the MVC architecture</blockquote></p>

That's it for the view. Just some raw html, nothing special. Pull up the about page now at ...index.php/about and you should see your html page

the View::forge('about') calls the file about.php in your views directory

the capitalization is important here, note that when naming your files.

View::forge() just returns HTML. So you could return any HTML and it would output. But the whole point is to load the HTML and data from the view.

So you made an HTML page.... "big deal, this is going backwards, i already know HTML. I think your blog is making me stupiderer" You can see the coolness here right? The view is just an HTML page, and next we'll add in data. So you can have a totally separate file for a designer to work on. They design the page all fancy, then you just go in and hook the data into it.

#FuelPHP #MVC

Controller... check! Grab a parameter...go

Let's modify our controller to grab a parameter passed in by the URL

Let's add a function to our basic controller in /fuelphp/fuel/app/classes/controller/about.php

<?php Class Controller_About extends Controller { public function action_index() { echo "This is my first attempts at MVC architecture."; } public function action_water() { echo "i'm thirsty"; } public function action_supme($name = '') { echo "hey whats up $name!"; } } ?>

The new function is called supme. Basically it's gonna say what's up to you, based on the parameter you pass in. So call the about controller with the supme function. ...index.php/about/supme Right now you get nothing. now try it like this ...index.php/about/supme/Jimmers **The capitalization on the supme part doesn't matter.

Oh nap! it said whats up to Jimmers.

It is taking anything after the supme function as attributes. This is opposed to the classic way of getting data using index.php/about.php?action=supme&name=Jimmers. I think it's a nice way of sending parameters, the other way is kinda ugly. you could extend the function to accept more parameters by adding more into the definition, like

public function action_supme($name = '', $address='', $age='21'...)

then to call function just add more parameters to your URL string ...index.php/about/supme/Jimmers/FakeStreet you can supply default parameters if you want as well.

So... you are just accessing _GET['name'] then... "big deal. I could do that before" Yea, but the framework extracts it for you cleanly from the function parameter. Now if we were using a view, we could clean it, sanitize it, and then pass it off to the view for display.

#FuelPHP #MVC

First steps: A Controller

So go to your main site (ex. http://localhost/fuelphp/public/index.php) including the index.php in your URL. This is your main driver for the site. It will handle all the routing of your different pages. So anything that comes after the URL, will be handled by your controllers. Add the following to your url and try to navigate there

http://localhost/fuelphp/public/index.php/about

You should get a 404 error. That is because we haven't setup a controller to handle that request yet. Controllers are simply a tool that fetches the requested data and serves up a view. It is the thing that a user will call, and it will communicate between your models and views. You could have JUST a controller with no models or views if you want. Let's do that to start.

So navigate to /fuelphp/fuel/apps/classes/controller/ This is where all our controllers will be stored. Create a file called "about.php" **note the lowercase, FuelPHP requires this filename to be lowercase! put the following code in the file.

//My first Controller <?php Class Controller_About extends Controller { public function action_index() { echo "This is my first attempts at MVC architecture."; } public function action_water() { echo "i'm thirsty"; } } ?>

Now push that to your server & reload the page, you should see some output to your browser.

The framework is handling the request to ...index.php/about by serving up the Controller_About class. So think of these classes as part of your URL

We could make any class here, Controller_Hello, then access it using ...index.php/hello.

We must use the prefix Controller_

We must also extend the class Controller

The capitalization on the word About doesn't matter.

the "action_index()" is the default function that Controller_About will call when requested. That is why it's output showed up when you requested ...index.php/about.

Access our Controller_About and the index function directly by appending this onto your URL, ...index.php/about/index

now try ...index.php/about/water

you should have gotten different output

so basically we are just accessing classes and functions in our URL's.

you need to prefix these functions with the word action_ if you wish to call them from the web.

you could easily place these in subdirectories, you just need to add the subdirectory in your class name. So if you put the controller in /fuelphp/fuel/app/classes/controller/test/about.php, your class name would be Controller_Test_About. Then you would access it using ...index.php/test/about

So we made a page echo? "big deal. i coulda done that in one line." Yea but we did some fancy pants stuff here. We have 2 different outputs from the same file, but different URLs. Let's do a little more with controllers

#FuelPHP #MVC

Initial setup

So i'm gonna assume you've got a box setup somewhere.

You are running some type of AMP(Apache MySQL PHP) server. :WAMP:MAMP:LAMP

You also installed MongoDB on this server, and downloaded and installed the FuelPHP source.

I'm gonna assume your base path is /fuelphp/

Make sure you realize there are 2 different view paths. One is to views and one to view models.

/fuelphp/fuel/apps/views - this is your views path /fuelphp/fuel/apps/classes/views - this is your view model path.

If you make a view, you want to use the views path. View models I will dive into later, but I don't think this is true View Models, like WPF XAML binding in .NET. (that's another beast)

Once you install make sure you can pull-up your site, it'll be something like http://localhost/fuelphp/public/

#FuelPhpMVCMongo #FuelPHP #MVC

Come with me on a journey through MVC and TIME

A little background on me, i always been a computer geek. Gamer mostly, but then I was intrigued by the internet and web design. I learned HTML, how to use cgi, then eventually some php/css/javascript. But the extent of my coding was mostly copy and pasting snippets or from tutorials, and hacking together things. I would never claim to be fluent in anything but HTML(not saying much). If that is your style of coding where google is your codebase/snippet base. Like me you can probably get projects done, but not as fast as that one guy who just knows the language like the back of his hand. I'm gonna try and make the flow of knowledge in the Copy Paste Coder style, but I recommend (something i've been doing on my own) is to just spend a little more time, dig a little deeper, and understand a little bit more about code you copy paste.

So i figure i need to brush up on my coding skills, so i'm gonna do some work. I been out of touch with things for a while, just slumped into my daily grind. So a lot of architectures ( which are now even kind of becoming stale ) popped up all over the web. I was familiar with php from my own dabbling, and am pretty confident in my abilities. But I didn't learn all the MVC (model-view-controller) stuff that was going around the nets. I kinda always built my own Model/View, but the controller aspect seemed unnecessary. I would just make my views do what the controllers did. As of starting this, I still feel like it's unnecessary to make controllers, but the whole point of this exercise is to learn why this architecture got so popular.

So i was writing a site, and kept writing a bunch of filters/loaders/classes, then it struck me. What about all these php frameworks? Some dood has already written all these, and perfected them through far more extensive testing then I was doing. So i tried out codeigniter, and i dug it, but the routing seemed to keep causing me headaches. I also didn't think it supported mongo DB. I am familiar with SQL and mySQL, so I wanted to learn one of these new JSON document oriented databases. I eventually found FuelPHP (shiny website, poor documentation) and decided to give it a go.

So come with me as I learn FuelPHP, MVC frameworks, and MongoDB all at the same time. (I may do a ruby series next) Feel free to post questions, ANY QUESTIONS, even STUPID questions. I'll try to get around to them, and hopefully we can both learn and help each other.

#FuelPHP #MVC

Trending Blogs

Recently Viewed Blogs

Copy Paste Coder