We have told them nicely tons of times
Last time I had that error, was an issue in the
->to($mail) section. In my case, the model was returning null and not finding the person to send the email too.
Captain wrong answer strikes again! Never fails...
Check your csft token, as well as your session mechanism is all working properly.
cmdobueno left a reply on Would Like To Know Developers Experience(Coding) And Age?
I think seeing the users track record.
Here is an example:
I look at the reply history of bobbybouwmann, and see a lot of extremely qualified replies, posts, and those things.
When I look at you munazzil I see a lot of wrong replies, same questions over and over, and the lack of an ability to find your own answers.
Age has very little to do with programming ability. I am 32, I know a programmer who is several years younger than me, who is at the very least equal to me on programming, but in reality, they are probably better.
Experience, yes that can be important, but school means little in this world. Schooling can help, but programming is a strange world.
See, you are right. All those that are listed have more exp in this system than I do. They have more time, patients, and ability to help people than I do.
I try to help when I can, and provide valuable input to people when I have the proper knowledge to assist. I try not to venture out of my the areas I can provide meaningful input.
You simply provide people the wrong answers. It is a waste of time. I am not going to sit here and argue the back and forth about my opinions of you. You asked a question, I gave my feedback. I do not play nice, kind, or anything like that. I am brutally honest.
You could spend the time watching lessons on here to better improve your programming ability, but hey that's just me.
Good luck on all your future projects.
after seeing so of your suggestions, i know to steer clear of sri lanka... you should not freelance. You should go back and learn more.
Laravel is a PHP framework. Laravel does not provide anything that could do XHR (yes its real name...) requests. Laravel does loosely 'suggest' use of VueJs which uses axios to handle XHR.
It is quite magically... you should watch tutorials, as it is quite obvious you do not know what you are doing...
cmdobueno left a reply on Composer Install Without 'composer.json', Is That Possible?
Thats like running php without php installed.
cmdobueno left a reply on Comment Table Structure For Guest And User Laravel
This has been answered about a 100 times, between here, google, and stack overflow. If you cant help yourself... why should we help you? Demanding our help, and complaining about it... well that gets you ignored.
You can turn off the token in middleware.
But yet, that is roughly what I am saying... use normal authentication, because that is what you are doing.
API is 'effectively' if not 'completed' stateless. It is kept known by tokens of one kind or another. I have never heard of using state (session authentication with an API... but I by no means an expert).
If i were you, i would keep things wrapped inside of web, because you are using these are web. That may solve all of your problems for the most part
just remember thati f you are using auth:api to change it to auth
If you want to do this, why are using API routes? You could just web-routes and life would be perfectly fine. You are just accessing the system with ajax/axios instead of the browser... calling this an api is wrong. Use web-routes and you will probably remove the vast majority of your issues.
And you do not have to use laravel shift, but to be 100% honest it is probably cheaper when it comes to upgrade cost compared to doing it youself.
Upgrade to php 7.2 on your server Use laravel shift (https://laravelshift.com/) to upgrade to laravel 5.7 Use any of those packages you would like.
Worst Case: You can not upgrade your php version so you are left with a choice: a. Stick with 4.2 (you should upgrade!) and custom code the above packages for your needs b. Use laravel shift and upgrade to the highest supported version of laravel and then custom code what you want.
I strongly advise using laravel shift to upgrade the project from 5.2 to 5.7, upgrading your php version, and being very very happy with the improvements! (And better package support!)... if you are worried about security, it is best to keep more up to date with laravel (at least be at the LTS version).
Laravel supports an infinite number of online users.
Your server configuration is the deciding factor in what you can support. IF you have a tiny little 1 cpu 1 core 1 gig of ram server running @ 10mbps then you number is considerably lower than a massive AWS cloud with load balancing and all that fun stuff running at 10gbps...
Its not laravel that decides these things, its the rest of your configuration.
So, why? Why use a button? What is the purpose of using a button that is being used like a link (a tag). Why are you not using an A tag? You are overly complicating code, and going to cause more breaking issues.... I do not understand. I mean this is quite literally stupid.
You are using too much ram in your php.
This is a standard php error that could have been found by googling it. Literally there is no reason you should be asking this standard php question that has been answered literally a trillion times here, on google, on stack overflow... all over the place.
Either fix the code that is consuming all the ram by running what is most likely an infinite loop, or increase your memory limit in php. Im not going to tell you how to increase your memory limit... and I swear you better not post that as a question... google it.
It appears you are doing with through a mysql query. You are, as it appears, taking too many records at once, or you are infinitely looping a relation. But you provided no code, so I am guessing.
Its not really a preferred way. Just people giving you the wrong advice.
First you do not, nor have you ever, added .blade.php to any of the @'s
Second from what I have seend, you should only ever use a single extend. You want @include.
@include is from the view root (I think the first reply said that... they had the best possible answer).
It just people either do not proof read their post very well, or are simply spreading false information.
And this is why we need to be able to rate responses...
The real question here is not what laravel can do for you... it is instead what can you do for laravel?
You can very easily build a small application, and use poorly constructed relations and queries and have that application grind to a halt. (Example: Non-optimized queries not using with properly can run 10k queries... but when properly using with they can run 5... and provide identical information...).
It really really really depends on the following...
I personally feel you can build an application that can do nearly anything. The real question out there should not be can laravel scale to complete X, Y, or Z... but instead at what point does it become better to use a different framework for cost of infrastructure vs profit.
You need to brush up on the basics of effectively everything. Its been what a year of your questions? Your questions are fine, up until you realize that in a year you havent learned anything. I am not trying to be a jerk, I am really not. I am just saying you need to watch some videos... this years worth of questions would have been explained in about 3 hours worth of the FREE videos on here or youtube. Please please please do yourself, and the rest of us a favor, and do a bit of studying.
I really think that would be a good idea @cronix hiding with enough downvotes. Now somebody just needs to convince the boss man.
Yes, but that is the wild world of the internet... and most places have some form of control or notifications to let a person know that the info is probably bad, or should be used carefully.
Directly allowing us to up or down vote can solve this problem...
The user's level is not a good example, you can boost your level by watching videos, and asking questions... so... this is another great example of why we need down/up voting
cmdobueno left a reply on Defining Gloabal Variables Through Helper Function Files
No. No its not. Globals are not your friend. They do have a purpose of course, but this is not their purpose.
There are lots of other things you can do: https://laravel.com/docs/5.7/blade#service-injection
Or use a view composer (this is probably the best) https://laravel.com/docs/5.7/views#view-composers
Do not use globals here... that is very poor practice.
It is not about outdated best answers needing to be updated.
What this is about, is people that barely understand what they are doing, thinking they know the right way, spreading a plague of misinformation.
As has been stated, this community is rather well grounded, but I have noticed a very real issue, of those that actually understand the system, simply not providing feedback anymore. The rise of extremely poor answers has grown significantly over the last few months, calling them out on honestly dumb answers is highly frowned upon.
I get it, we live in a world where we need to treat everybody as if the world really cares about that them. We need to treat them like an employer would be okay with a dumb solution, and thats fine, I can let them find out the world is cold. But, without the ability signify bad solutions by the community, we are going to begin to improperly educate those that want to do things the right way.
I agree it is a positive place. Myself personally have been pushed away from using it as much as of late, lets say the last 2-3 months because I am finding less and less value in the answers being provided.
Or, an answer is so poor, I am put off from the entire thread. There is no way good way to respond, you can not really call the person out, they just ignore it, or it causes drama... and I have no need for drama.
A down-vote provides a good method to allow a person to weed out poor responses, and up-vote provides the exact opposite.
Again, maybe I am wrong, and a large part of this request comes from personal opinion, so it is possible it is not the best course of action, but I feel like we need some way to flag these bad replies.
Agreed, I do not do peoples work for them... unless they want to pay me... but I feel like being able to down vote would help to isolate the very poor responses I have been seeing lately. Responses that are not even closely related to the question posed. I am not going to throw out anything too specific because I do not want to call anybody out.
Could it be considered to add an up/down vote to the discuss threads? Lately, I have noticed a large number of very poor replies to threads. I am not saying that people should no have input, but we need a way to better warn those coming to the forums of the poor solutions and what is considered better practice. I mean, maybe having this work with Best Reply is possible.
Basically, (and maybe it is just me), I would love to be able to mark good answers as just that, and bad answers as, well honestly bad. I think in the end it will help the community.
If anybody else has any feedback I would love to hear it.
Glad I could convince you. That is excellent. Webpack is very helpful.
Everybody that hates on webpack makes me laugh. Webpack is great at what it does, but does have some learning curve to it... some people just refuse to adapt to the times though...
window.$ = require('jquery');
laravel task scheduler:
as with basically everything in laravel, they have made it extremely easy.
hahaha, you are missing the entire point... as normal.
Never did I say, nope, you cant use temp tables... or temp files... or AI to solve the problem.
What I am saying, is your answer provides very little clairity on the issue, unless somebody fully understands how to use VB... and that is not everybody.
While, yes, there are a large number of us on the forums that totally understand multiple languages, that is not everybody. They are here dealing with PHP, or JS, or whatever... I am just saying that, no matter the correctness of your answer, it is like giving somebody an answer in a different language.... because that is what your example was...
Additionally, I showed you respect by not being a condescending fool... different ideas to solve a problem are awesome... anyway... good luck.
No, he asked a question about about php (lets call this spanish), and you answered in VB (lets call this french).
But im not going to destroy this guys thread... so yeah... @cronix has a good enough answer.
Alright, got a bit of an interesting question.
I have two systems, 1 is an API, the other is a frontend. I am trying to figure out how to stay logged in on the frontend system. I have given thought to using the users table, and when a user connects to the API, does their authentication, they front-end system will just 'create' a user for them and authenticate them that way. Storing the required tokens and all that.
I am just not sure if that is reasonable or not.
I personally prefer phpstorm, but this is rabbit hole of person opinions, and people being super easily offended about how much better their IDE is over what everybody uses.
Kinda funny though... I still like sublime. I just like phpstorm more, and having some much out of the box is nice, at least for me. And its free... for me... so thats cool.
I suggest this, because it is possible you are auto-loading the old classes, and this going to their old location, which is why the changes do not count.
So you want to pretend like you have people using your system? So you want to magically generate them so poor saps buy your stuff?
It all depends what data you have. What your security requirements.
I generally do not encrypt much data. Sometimes I will encrypt names or addresses because I am required too.
Remember that when encrypted there is no good way to search for that data. It will slow down queries.
It is very good advice.
I have moved away from Model::get() and towards Model::get(['id','name',...]);
There are only specific times i want all fields, and those are actually somewhat rare, example being an edit page for a user. But in all honesty, I still do not want all the users fields here... I do not really need their timestamps (created/updated_at). Additionally depending on your routing, you may not even need their ID, because this could be do via your route model binding.
It is important to understand how to best utilize sql. It was something I was extremely against (using DB or Raw queries) for a long time. I use them more and more now, but again, purpose and place are important.