Hello Sir. Now it's 2023, I started watching your courses. I want to tell you that I learned many things that were difficult for me until now. Thanks for what you do and don't stop.
Glad to hear that man. This course and others are designed to be evergreen. That is why I am not using any of the "fancy" or modern libraries or functionality. Pure basics, concepts and principles that have been around for decades. And you can always improve your code on your own while still following this course :) Are you working with php already, or still learning?
@@ApplicableProgramming Yes! I've been studying webdev for years but I'm not a very good programmer. I struggle with dynamic web generation and the MVC architecture. I understand the concepts but I am not able to concrete its implementation correctly. I tend to make a mess myself and at some point dump all my spaghetti to the bin. But in these videos you explain it really well. Thank you so much! I need more practice!
Really enjoy the tutorials. My only critique is some developers/UA-camrs make the text size bigger in the editors and that helps us see it a little better. Especially if we’re viewing on mobile devices.
Thank you for positive (and constructive :) ) feedback. I have increased the text size a bit more in the latest videos so it should get better :) If you come across some tutorial where you like the text size, please send it to me so I can compare the text size and adjust even more
Great stuff! Thanks! Only thing I'm missing so far is structure. For example, I'd insert a video in front of ones that are on line now. Video that explains how would professional dev organize folder/file structure. I mean, no one just starts to write a custom CMS without thinking first and laying out architecture. That said, I get it. This tut series is not for absolute beginners. Although I can follow tuts with ease and understand it with no problems whatsoever, I can see how some people could get lost. BTW I have same "problem" with my junior colleagues, I often forget that what is for me a piece of cake, for them is something that's almost comparable to magic. :) I guess my main point here is that OOP paradigm shift from procedural programming is biggest bite to chew. PS nothing personal, keep rockin', and thanks one more time.
Thanks Petar, that is actually a very good point, I could have spent a bit more time on that. Although, my "philosophy" is that one should have a good enough control over the code in order to not be scared to change the folder structure as needed, because refactoring is expected and welcomed operation as it is always improving the code quality. Because, the folder structure has actually changed at least three or four time so far, and will probably change more depending on how people want to proceed with the project in the future. We didn't have modules, but now we do. We still do not have plugins, but maybe one day we will. So... And each lesson improves the project a bit, but still keeps it functional at every step, so that people can learn why things are being done, rather then just fallow some random dude on youtube "this is how you should do it" :) But please keep the suggestions, that is how I improve this project, it is not that I have a goal in mind, it is just a way of... making a bunch of videos and explaining concepts :) Btw, I noticed a lot of people from Serbia/Balkan, did you search for PHP CMS on UA-cam directly, or have you found the video shared some place? Just curious :) Pozdrav
@@ApplicableProgramming I understand where you're coming from. As every senior dev knows, one project is never finished, it is only polished enough for production. Refactoring is always somewhere there, hovering over TODOs. And I must say that I agree fully when you say there is no "right" way to "do it", especially when it comes to the MVC approach. I guess what I wanted to say is that mentioning folder/file structure wouldn't hurt. :) When particular section in the tuts is finished, than show how to refactor and remodel architecture. That is good for quite a few reasons. Most important IMO is reiteration over already "learned" stuff, and that cements concepts in the mind, especially if done as "homework". Because, if one thinks about it, any concept is an abstract entity, and to "materialize" an abstraction you have to use it and see it in its intended environment. Regardless, This is great tutorial series because it deals with real "real world case" and I must say I genuinely appreciate it.. As far as it goes for me searching for PHP tuts, I've spent last few years in JS ecosystem (NodeJS), barely touching PHP. Than I've learned and read about PHP 8, and decided to learn differences between 7 and 8, do some benchmarks, write a package for Laravel or an "app". I must say I'm impressed but also struggling with, for example, attributes and how to use them in real world. So there you go, I've searched for PHP 8 OOP and your series popped up. BTW I am coming from PHP and I just love it. I am genuinely happy that it's coming back big time. Community is getting vibrant again and there is nothing you can't build with modern PHP, and best of all, it just works ... everywhere. PS Odlucio sam da pisem na engleskom jeziku zbog internacionalne publike. Mozda neko pokupi nesto korisno iz nase prepiske. :) Pozdrav i tebi i sve najbolje. :)
@@pasizdobrekuce Yeah, I agree with pretty much all you are saying :) I must admit I am not that in trend with all changes and new features php 8 has (nor am I actually trying), but there are definitively some very cool things that warm my heart. If I may ask, do you work for a consultant company (making software for clients) or do you make things for "yourself"?
@@ApplicableProgrammingThank you for the replay🙏🙏🙏. One of the thing that im having difficulty with is the concept of 'Query string'. I would love to see abt it
@@-dinkadink6735 You mean the one in the url? That is basically just "everything" that is in the url after the website name. When you type some web address (or click on a link), you are asking some server for some website, some page of a website. Asking means the same as "querying" , and sometimes you need ask server (query server) with more specific details of the page, like "Give me only the contact the page from this website", which you use Query Parameter for like page=contact, or section=contact in our example. And sometimes you might have to go more specific like "I am Yasin, returning visitor of this website, I want to see a contact page" which would be something like ?user=Yasin§ion=contact . And that is your query string, everything after the first question mark. Look at this graphical explanation, it might help you visualize it mixpanel.com/blog/community-tip-adding-properties-into-the-url/
@@-dinkadink6735 No problem, glad I could help :) Btw, I am trying to build a community in one facebook group facebook.com/groups/applicableprogrammers/ currently not much is happening because I am focusing on these videos, but if you would like to join the group of Applicable Programmers that would be great. You can ask much more questions there, and maybe add some people who are trying to learn. The groups is still at the beginning, but it will be purely about learning web dev, as well as career discussions, so no spam job offers and other spam, I hope
Dear teacher,I am having issues with the inheritance Fatal error: Uncaught Error: Class "Controller" not found in C:\xampp\htdocs\CMS PROJECT\Public\Controller\aboutUsPage.php:3 Stack trace: #0 C:\xampp\htdocs\CMS PROJECT\Public\Index.php(10): include() #1 {main} thrown in C:\xampp\htdocs\CMS PROJECT\Public\Controller\aboutUsPage.php on line 3
You mean in one file? I would say yes, but I do sometimes make few classes in one file, although rarely. Why would you do that instead of just making another file?
@@ApplicableProgramming I check If the page was accesed through post method, than it would be obvious, the form was submitted. Orherwise, i display the form.
@@MrGigi-dz9cv Sure that is one way of doing it, but it has its limitations. I recommend checking the first video of the series MVC to see some advantages of separating the concerns. Most dominant is rapid and parallel development. The moment more people start working on a project, it becomes very difficult to maintain html+php+css in single file.
Thank you for feedback, I will try to slow things down in future videos. You can also adjust playback speed in youtube player so that it plays a bit slower
![5. PHP MVC View & scope | Build a CMS using OOP PHP tutorial MVC [2020]](http://i.ytimg.com/vi/viu50QhQtI4/mqdefault.jpg)
Great, more please and your type speed is insane
Thanks. Everyone can be that fast, with a bit of magic in video editing ;)
@@ApplicableProgramming 😅
@@ApplicableProgramming 😂😂
Hello Sir. Now it's 2023, I started watching your courses. I want to tell you that I learned many things that were difficult for me until now. Thanks for what you do and don't stop.
Glad to hear that man. This course and others are designed to be evergreen. That is why I am not using any of the "fancy" or modern libraries or functionality. Pure basics, concepts and principles that have been around for decades. And you can always improve your code on your own while still following this course :)
Are you working with php already, or still learning?
@@ApplicableProgramming Thanks for the feedback. Right now I'm just learning PHP and I am going to work in this direction in the future
"It just works automagically!" Thank you, sir, for this awesome lesson.
Glad you liked it Gustavo. May I ask why do you like this tutorial?
@@ApplicableProgramming Yes! I've been studying webdev for years but I'm not a very good programmer. I struggle with dynamic web generation and the MVC architecture. I understand the concepts but I am not able to concrete its implementation correctly. I tend to make a mess myself and at some point dump all my spaghetti to the bin. But in these videos you explain it really well. Thank you so much! I need more practice!
how come no one mentioned the joke at the end 😂 I like it as the whole video thanks
hehe, I guess people do not pay enough attention to details :) thanks for sticking to the end btw :)
We continue with our CMS by making main controller, and reusing its code with inheritance.
Really enjoy the tutorials. My only critique is some developers/UA-camrs make the text size bigger in the editors and that helps us see it a little better. Especially if we’re viewing on mobile devices.
Thank you for positive (and constructive :) ) feedback. I have increased the text size a bit more in the latest videos so it should get better :)
If you come across some tutorial where you like the text size, please send it to me so I can compare the text size and adjust even more
This guy should be a lecturer. He just simplified inheritance without using any jargon.
Thank you very much Philip, that is very nice to hear. I do try to use simplest possible wording, very glad you noticed..
Great stuff! Thanks! Only thing I'm missing so far is structure. For example, I'd insert a video in front of ones that are on line now. Video that explains how would professional dev organize folder/file structure. I mean, no one just starts to write a custom CMS without thinking first and laying out architecture. That said, I get it. This tut series is not for absolute beginners. Although I can follow tuts with ease and understand it with no problems whatsoever, I can see how some people could get lost. BTW I have same "problem" with my junior colleagues, I often forget that what is for me a piece of cake, for them is something that's almost comparable to magic. :) I guess my main point here is that OOP paradigm shift from procedural programming is biggest bite to chew.
PS nothing personal, keep rockin', and thanks one more time.
Thanks Petar, that is actually a very good point, I could have spent a bit more time on that. Although, my "philosophy" is that one should have a good enough control over the code in order to not be scared to change the folder structure as needed, because refactoring is expected and welcomed operation as it is always improving the code quality. Because, the folder structure has actually changed at least three or four time so far, and will probably change more depending on how people want to proceed with the project in the future. We didn't have modules, but now we do. We still do not have plugins, but maybe one day we will. So... And each lesson improves the project a bit, but still keeps it functional at every step, so that people can learn why things are being done, rather then just fallow some random dude on youtube "this is how you should do it" :)
But please keep the suggestions, that is how I improve this project, it is not that I have a goal in mind, it is just a way of... making a bunch of videos and explaining concepts :)
Btw, I noticed a lot of people from Serbia/Balkan, did you search for PHP CMS on UA-cam directly, or have you found the video shared some place? Just curious :)
Pozdrav
@@ApplicableProgramming I understand where you're coming from. As every senior dev knows, one project is never finished, it is only polished enough for production. Refactoring is always somewhere there, hovering over TODOs. And I must say that I agree fully when you say there is no "right" way to "do it", especially when it comes to the MVC approach. I guess what I wanted to say is that mentioning folder/file structure wouldn't hurt. :) When particular section in the tuts is finished, than show how to refactor and remodel architecture. That is good for quite a few reasons. Most important IMO is reiteration over already "learned" stuff, and that cements concepts in the mind, especially if done as "homework". Because, if one thinks about it, any concept is an abstract entity, and to "materialize" an abstraction you have to use it and see it in its intended environment. Regardless, This is great tutorial series because it deals with real "real world case" and I must say I genuinely appreciate it.. As far as it goes for me searching for PHP tuts, I've spent last few years in JS ecosystem (NodeJS), barely touching PHP. Than I've learned and read about PHP 8, and decided to learn differences between 7 and 8, do some benchmarks, write a package for Laravel or an "app". I must say I'm impressed but also struggling with, for example, attributes and how to use them in real world. So there you go, I've searched for PHP 8 OOP and your series popped up. BTW I am coming from PHP and I just love it. I am genuinely happy that it's coming back big time. Community is getting vibrant again and there is nothing you can't build with modern PHP, and best of all, it just works ... everywhere.
PS Odlucio sam da pisem na engleskom jeziku zbog internacionalne publike. Mozda neko pokupi nesto korisno iz nase prepiske. :) Pozdrav i tebi i sve najbolje. :)
@@pasizdobrekuce Yeah, I agree with pretty much all you are saying :) I must admit I am not that in trend with all changes and new features php 8 has (nor am I actually trying), but there are definitively some very cool things that warm my heart. If I may ask, do you work for a consultant company (making software for clients) or do you make things for "yourself"?
Thank you !
automagicaly kkk, awesome job on explaining why and how to use OOP
Glad you liked it :)
This is a pretty helpful way to explain !! thank you for this
You're very welcome, glad it helped!
Are you following the entire series?
@@ApplicableProgramming Yes :) I am planning to finish it this week
Thank you man.
Hope you will come with more content
Thank you for your comment, new video in php is comming during the week (or two :) )
Is there something you would like discussed a bit more?
@@ApplicableProgrammingThank you for the replay🙏🙏🙏. One of the thing that im having difficulty with is the concept of 'Query string'. I would love to see abt it
@@-dinkadink6735 You mean the one in the url?
That is basically just "everything" that is in the url after the website name. When you type some web address (or click on a link), you are asking some server for some website, some page of a website. Asking means the same as "querying" , and sometimes you need ask server (query server) with more specific details of the page, like "Give me only the contact the page from this website", which you use Query Parameter for like page=contact, or section=contact in our example. And sometimes you might have to go more specific like "I am Yasin, returning visitor of this website, I want to see a contact page" which would be something like ?user=Yasin§ion=contact . And that is your query string, everything after the first question mark. Look at this graphical explanation, it might help you visualize it mixpanel.com/blog/community-tip-adding-properties-into-the-url/
@@ApplicableProgramming Oh thank you very very very very ....... much.🙏
@@-dinkadink6735 No problem, glad I could help :)
Btw, I am trying to build a community in one facebook group facebook.com/groups/applicableprogrammers/ currently not much is happening because I am focusing on these videos, but if you would like to join the group of Applicable Programmers that would be great. You can ask much more questions there, and maybe add some people who are trying to learn. The groups is still at the beginning, but it will be purely about learning web dev, as well as career discussions, so no spam job offers and other spam, I hope
Thank you for this lesson :)
Thank you for watching John :)
Are you learning php from start, or are you already familiar with basics?
@@ApplicableProgramming I know some web dev basics, trying to finish my junior dev test and your lessons help a lot with that :)
@@johnwela1928 glad for that! :) ask if you get stuck or you have something that is not covered in this series
Thank you
My pleasure :)
Are you following entire tutorial, or just inheritance?
Nice
Thank you Raj!
Dear teacher,I am having issues with the inheritance
Fatal error: Uncaught Error: Class "Controller" not found in C:\xampp\htdocs\CMS PROJECT\Public\Controller\aboutUsPage.php:3 Stack trace: #0 C:\xampp\htdocs\CMS PROJECT\Public\Index.php(10): include() #1 {main} thrown in C:\xampp\htdocs\CMS PROJECT\Public\Controller\aboutUsPage.php on line 3
Hey, have you included the Controller where it is needed?
@@ApplicableProgramming I resolved it already sir. I spelt the controller in a wrong way that was why it affected my code
Would it be wrong to have everything in one page ?
You mean in one file? I would say yes, but I do sometimes make few classes in one file, although rarely.
Why would you do that instead of just making another file?
@@ApplicableProgramming I would just output some html, rather than having more files.
Also, easy to output error messages.
I find this more practic
@@ApplicableProgramming I check If the page was accesed through post method, than it would be obvious, the form was submitted.
Orherwise, i display the form.
@@MrGigi-dz9cv Sure that is one way of doing it, but it has its limitations. I recommend checking the first video of the series MVC to see some advantages of separating the concerns.
Most dominant is rapid and parallel development. The moment more people start working on a project, it becomes very difficult to maintain html+php+css in single file.
Too fast not enough explanation on what you are doing.
Thank you for feedback, I will try to slow things down in future videos. You can also adjust playback speed in youtube player so that it plays a bit slower
so confusing
Which part in particular? Code, presentation, video, CMS?