There are two concepts we're dealing with, the first being a code repository. Although there are different types of repository technologies, GIT is the defacto standard currently. Websites such as Github and Bitbucket are popular web services offering free GIT hosting solutions. The key point here being GIT is the actual underlying technology, and will ...
Well, my personal preference is...it depends on what exactly need to be debugged.
If it's a simply element that's not displaying correctly due to some odd CSS, I'll simply get the live site running, open Firebug and sort it out.
If it's a PHP or JS related issue, I normally tend to take a copy of the site and run it on my local host. This is always the ...
I am far from being a sophisticated developer and I also do debugging in online sites.
I use this marbelous tool
It have a lot of advantages over a single var_dump.
Hope it works for you too.
There's multiple settings in PHP and Apache that can cause timeouts.
From your error message, the issue is not the PHP Max Execution time, but with FastCGI. This is a programming interface on Apache web servers that is used to improve server performance.
The error is in your host's FastCGI configuration. Check the value for FcgidIOTimeout, which defaults to ...
Sometimes there are subsequent actions that take away the focus without displaying the var_dump statement. There are two ways I use to view debug information in these conditions. First you can follow your var_dump statement with an exit() statement. Include a string if you need to know which exit statement was used (ie: exit('here'). The other option is to ...
As of 3.6.3, the Joomla core templates will give you the stack trace (including any nested Exceptions of the top level object that ultimately gets caught by the error handler) when the site is in debug mode. Of course, such a feature is also dependent on the template supporting it if it has a custom error.php layout.
This is kinda of necroposting, but an issue still has no fix from Falang author, so here is it. In the file ./plugins/system/falangdriver/falangdriver.php
Find (309 row for Falang 2.6.0):
Now Joomla debug information will contain all queries. The fix has been submitted to Falang author as well....
Found out that the joomla database driver is being overridden by another one which belongs to Falang component that allows you to manage all the content translations. Falang database driver has no debugging implementation and thus only disabling the Falang while debugging the site would solve the issue.
Some third-party plugin may be generating the zero.
It is not a module or component output, because it should be included in the html
Since zero is generated after the Html, it is rendered before Joomla ends the execution, for example closing sessions.
I would disable, one by one, all non-core plugins (and everything else) to discover the cause.
The dreaded 500 error is the bane of my existence. If your error reporting isn't kicking out anything, the first thing I usually check is the htaccess file to see if it's the problem. In your case, you can still get to things, so I suspect that's not the issue.
The next thing I do is start uninstalling and reinstalling, or upgrading stuff. I've had the ...
I know this isn't a great answer, and the results you get will be relative, but I'd suggest perhaps installing a vanilla Joomla install on the same server and doing a comparison of output from the memory debug tool. If your main site is eating up memory whilst the vanilla install isn't, gradually load in the same components and data and profile the ...
I often just use die($variable);, which should work in your case - break is just for loops. NB I'm not saying this is the best way, and I'm interested to see if other users have better ways of debugging.
I'd also recommend you look at the J!Dump plugin for what you are after. This gives a lot more information when you dump something.
If you're doing a lot of Joomla development then using a symbolic debugger within an IDE is indispensible in my opinion. It takes a bit of effort setting it up, but repays the effort multiple times over.
There are some guidelines at https://docs.joomla.org/How_to_debug_your_code about how to set it up, and you can hopefully adapt what's there to your own ...
There's a sourcerer tag used in the facebook og tag generator. If you switch the view source you can see it like this:
Could that be a use case for Docker?
Run official Joomla docker image in a specific version, and you can swap for another version for testing various environments
If a specific website is using the extensions, a snapshot of the website can be turned into a docker image
Docker image should have xdebug ready to go and be able to remote debug. Visual Studio ...
My question was answered in the comments section by user TryHarder. I'll formulate it as follows:
The approach I'm using is this:
Take a copy of your component and install it;
Remove the installed component folders within your Joomla installation (administrator/components/com_component, components/com_component, media/com_component);
Then create symbolic ...
Once a user recomend to me build a development environment using Ant
How to version a Joomla component
Also, you can build a structure usint git submodules. Where the project will be split in the joomla folders, and somewhere you'll keep a master git project for each components with all the submodules togheter. This will become the zip file
First of all, if you are going to move the site to another one, I highly recommend you to use Akeeba Backup.
There is a free version and it would make moving your website a lot simpler, while reducing the possibilities of a number of issues/errors compared to when moving your site manually.
At the hand, open your configuration.php and check everything it's ...
Have you tried echoing anything instead of the var_dump? For example, you can have something like echo('here'); or die('here');.
I think the likely issue is that your code is not even reaching the var_dump line, and that's why it's not printing the variable.
To fix this bug, you can edit the mod_articles_categories.php and add
this line after the defined('_JEXEC') or die;:
JLoader::register('ContentHelperRoute', JPATH_SITE . '/components/com_content/helpers/route.php
I can reproduce it in Chrome 49. The page jumps slightly to the right on page load. It could relate to the scrollbar which pops up later. Only happens when the page loads relatively fast.
Captured it on 2 screenshots:
It's a known problem for centered web sites with different CSS hacks to fix that, for example force the scrollbars to appear always:
As far as I know this is a Xdebug limitation and it should no longer occur in the most recent Xdebug version (at the time of this writing
[2015-06-19] — Xdebug 2.3.3).
Let me know if updating Xdebug brought any improvement.
Performance is a big subject. However, this article, from Roberto Segura Blog, shows a practical case to answer your question.
Joomla! rendering tools benchmark