am a newbie in laravel. When working out with samples most of the error shows message in a page called container.php. inorder to debug, using an extension that shows debugbar.would like to know is it possible to do line by line debugging in laravel and identify exact error of the code written in any way? Using visual studio code editor.
Laravel has its own debugging system. you can use built in dd() function, And there are several packages that can be used to debug Laravel projects. Here are some links and hope that it will be helpful for you.
02-04-2014-package-laravel-debugbar
barryvdh/laravel-debugbar
You can use laravel-debugbar package
Laravel-DebugBar
this will show all the SQL query you are running all the route and all the errors just like Chrome Developer Console
You can go through the entire sorted call stack and all details as arguments provided, function names, through the error page displayed. That error page is everything a programmer needs to understand what went wrong with the request and you will get used to it as soon as you fix an issue for the first time. Below I give some tips
Made an error on Provider folder file by appending '1' to the class filename on code.,
As the error is now on Provider file, it was expected to show that file in the stack trace.
Please see the screenshot attached where the error file is not shown, only laravel builtinfiles.
Related
I'm having an issue with a Joomla site, It was recently upgraded to Joomla 3.0 but now the home page hows the error "undefined method Joomla\Registry\Registry::getValue()", the only issue is it does not tell me which files are throwing this error.
I have run a file search in cPanel and a grep at command line to find any files with "getValue" in them but all responses are 0. I've even checked the database, just in case a previous developer put it in there but I have nothing.
I've searched the web, checked error logs, disabled plugins and pretty much bashed my skull against the wall for the last week to no avail.
Can anyone help?
I working on the updated site here: http://dev.hershmanlegal.com/
In the backend of your Joomla site, try going to System > Global Configuration > Server, change the error reporting to Maximum and see if you get more details about the source of the problem.
If still no joy, check your server error logs.
Good luck!
I'm getting an error in the admin page when I try to login, it was working fine and I would like to know if you can please help find out what may be causing the error and how to fix it. The error is:
Fatal error: Class 'Magpleasure_Filesystem_Helper_Data' not found in /home/site/public_html/app/Mage.php on line 546
The admin page is only showing the header and the error line code, the search box but the search box is not giving any results neither. However, the front of the store is working find, no issues in front. Please help, thank you
Best Regards,
Jenny
99% that you were hacked and that you didn't apply the two patches which were released by magento some weeks ago...
I have seen that issue 1 day ago at a client side of mine and they also didn't apply the patch.
check also this: https://magento.stackexchange.com/questions/64461/error-logging-in-the-admin-panel-fatal-error-class-magpleasure-filesystem-help
It also happened to me. Did not install the security patches.
Follow the steps from this post:
https://magento.stackexchange.com/questions/64461/error-logging-in-the-admin-panel-fatal-error-class-magpleasure-filesystem-help
Remove all files: app/code/community/Magpleasure/Filesystem/
Clear your cache, login should be possible now.
Check for new "Admin Users"
Patch your System with SUPEE-5344!
This happened to my site AGAIN, even after removing the magepleasure files, and then installing the 2 security patches.
I looked in the community and local folders as noted above in the way that I fixed this the first time around. This time there was one called Ma2.
I deleted the files from both places and deleted the cache folder contents on the server. I was then able to get the backend again. There was another unauthorized user, deleted it.
There is a remaining problem though. Anybody know where to look to fully delete the problem?
This is Compiler Error edit index.php, there just comment out following lines
$compilerConfig = MAGENTO_ROOT . '/includes/config.php'; if
(file_exists($compilerConfig)) {
include $compilerConfig; }
it will fix now..
This looks like an extension has been installed but not completely. The error is because Magento is trying to find the file Magpleasure_Filesystem_Helper_Data which I guess will either be under code base local or community app/code/local/Magpleasure/Filesystem/Helper/Data.php but the file is not there.
I would suggest reinstalling the extension either by magento connect or locally and deploy to your system and if you are still having issues contacting the developer directly may be your best bet.
First off, ScintillaNET v2.6 was installed as a control and I have been able to use it and compile, so I assume the installation is ok:
This app is targeting the full .NET 4.0 framework, not the client profile)
Environment variable
ScintillaNT folder content
The error message:
The code triggering the error:
The error happens on the second line when I "step-in" the load method. Looks completely unrelated, but highly reproducible: the error always happens at that exact step.
The problem turned out to be a corrupted XML file. I still don't know why the crash page was all about ScintillaNET, but it appears this had nothing to do with Scintilla.
I am not deleting this question because I could not find any indication that this could happen (errors in different parts of the code triggering a Scintilla error page) and it would have saved me a lot of time trying to track back the "scintilla" problem.
We've been using protobuf for a while at work and I decided to write a little console app for a client which would allow them to do some testing on site.
I started a new c# console app and downloaded google.protocolbuffers and protobuf-net from nuget.
What I'm trying to achieve is to turn my "messages.proto" file into "messages.cs"
I've tried to get the protobuf to build the messages file on a prebuild event but with no success, it seems the command arguments have changed since our first implementation. I followed the example here
http://code.google.com/p/protobuf-csharp-port/wiki/ProtoGen
And added the following pre build event
"$(projectdir)packages\Google.ProtocolBuffers.2.4.1.473\tools\protogen.exe" --proto_path=./protos protos/messages.proto --include_imports -output_directory=./
However I get the following error
Input file protos/messages.proto doesn't exist.
I've tried all sorts of combinations but nothing seems to work. Am I approaching this all wrong or is there a gotcha here? Any help much appreciated!
Have you tried using the absolute paths? I vaguely recall having a similar issue myself that turned out to be an issue with it not resolving relative paths correctly.
I’m having trouble to find a bug in my application.
The problem is random and don’t throw any error. The web site just keeps loading and loading and eventually gets a timeout.
Is a web application using MVC 3 in VS 2010 Pro.
Some time ago, I see a friend to write something in the url, and gets all the trace of the program…
Sadly, I don’t remember what the command was.
Anyone has an idea of what command is it?
Any suggestion on what to use to debug?
Thanks!
Edgar.
UPDATE!
I finally found the command... is trace.axd
But Its behave the same way... sometimes load without problems and show me all the trace info... and sometimes.. it keep loading and loading...
Maybe something related with IIS?
Turn on break on every thrown exception, run your application in debug mode and wait. If it executes too long then pause application and check where you are or wait for exception that is handled somewhere.
Your friend may have had something like the following built into his application, to dynamically set tracing on.
Trace.IsEnabled = Request.QueryString["trace"] != null ? true : false;
This provides info only if the page is fully loaded. It's probably best if you use the VS debugger to step through code.
If all you loops look ok, investigate code that could result in circular references or deadlocks. These can be difficult to spot sometimes, look for functions or constructors that require results from a calling class. So code that needs the result from a function which in turn need results from the first.
Well, this sounds like you have an infinite loop somewhere.
Look at the code that runs when you visit the URL that gives you trouble. See if there is any loops in there (for/while). If yes, see why if they never exit. You can do this by putting a breakpoint inside the loop and examining its behavior over the iterations.
in MVC the bugs you do not see are most of time (especially in Razor and Ajax work) view compile errors. Sometimes syntax bugs on views just does not show that view and do not stop working.
Try that:
put a breakpoint in view.
If program stops in there it means this view is working. Othervise there is a syntax error in this view.
Another way to see some bug information more than in visual studio is use browser tools.
I use google Chrome. Just open developer tools in it. Open network. And do your request. It will list the requests and responses. Click the response and see the information. After style (it is written Verdana etc) read exception details. Sometimes there is more information :)
I am using MVC 3 in Razor from start. So this is a small bug in asp.net mvc.