all of a sudden some of the magento template like 1column failing to load.
Did anyone face this?
2014-04-02T15:12:33+00:00 DEBUG (7): Failed to load template:/home/wor/public_html/app/design/frontend/mytemplate/default/template/page/1column.phtml
Template path is correct and casing is also correct.
The error Failed to load template is not a part of stock Magento. Magento's can't load a template error is
Mage::log('Not valid template file:'.$fileName, Zend_Log::CRIT, null, null, true);
Also — notice that when Magento can't load a template, it uses the Zend_Log::CRIT error level, and not the DEBUG (7) level.
Both these signs point to some custom code (either an extension, local code pool override, core hack, or template customization) in your system that's making the template not load. Search your codebase for the Failed to load template string used with Mage::log. Once you find it, the context of the surrounding code should help you understand why Magento can't load your template.
Related
I created a plugin with custom blocks. I am have trouble with the block preview. When I set the block on preview mode and reload the page editor — I get a error message on all the blocks I've preview Error loading block: You are probably offline.
In the console I am also getting the following errors:
pd-admin.js?ver=2.20:12 Uncaught TypeError: jQuery(...).live is not a function
Failed to load resource: net::ERR_CONNECTION_CLOSED
wp-auth-check.min.js?ver=5.5:2 Uncaught TypeError: Cannot read property 'hasClass' of undefined
Any ideas what I am doing to cause this?
I find issue with the RichText field — if the RichText is too long I can't preview the block at all and in the block I get the same error message saying Error loading block: You are probably offline.
To fix console error : WordPress 5.5 stopped using jQuery migrate. This change has been causing problems with old plugins and themes. If you are noticing issues after upgrading to WordPress 5.5, installing this plugin might fix it: https://wordpress.org/plugins/enable-jquery-migrate-helper/
For RichText long text error, you need to increase LimitRequestLine in your apache configuration. Ref : how to increase Apache 2 uri length limit
trying to create a custom theme with bitnami XAMPP using magento devdocs
https://devdocs.magento.com/guides/v2.2/frontend-dev-guide/themes/theme-create.html
I get this error when I try to access the admin panel
There has been an error processing your request
Exception printing is disabled by default for security reasons.
Error log record number: 1130478184
I think you have to first check in your error log number "1130478184" where you exactly know what is the issue. I think from your given link which you refer your issue must be occured from theme.xml file's <preview_image>media/preview.jpg</preview_image> line. You have to try with comment following code in theme.xml file:-
<!--media>
<preview_image>media/preview.jpg</preview_image>
</media-->
I am developing a component in joomla 2.5, my component sends a request to some url and gets the response object. If i pass wrong url, joomla takes me to the default page of Error : 500 - No response code found . I want that if user install my component and mistakenly they put wrong url , it should show some custom error message/page which should more meaningful to non-programming person rather than taking user to default error page. Is there some way to add this type of functionality in Joomla without editing template/error.php file in core.
You should have an error.php file in your template, if you don't add one and make it look the way you want. also remember that when you turn debugging off you won't get the stack trace etc.
However error 500 indicates something different than that the url does not exist ("wrong URL"), which would be a 404. 500 is an internal server error and you need to check your logs to figure out what is causing it.
I have build my own component. I know very well about these stuff but all of sudden I wonder that the joomla request to my custom component is not displaying anything. Its displaying blank page.
See this:
http://designsoft.bestplacestestserver.com/index.php?option=com_marketplacemanager
Here is the very initial code of 'marketplacemanager.php' file of component where the request is not arriving. Don't know why.
Code - marketplacemanager.php
defined('_JEXEC') or die;
jimport('joomla.application.component.helper');
echo 'aa'; exit; // should have something displayed as here
Go to global configuration. On the server tab turn error reporting to development. Reload the page. Most likely you will now see the error.
Try this, replace the first line of your code with:
defined('_JEXEC') or die('why is blank?');
If still does not show anything it means displaying errors on your server is locked, so checking the error log would be the only option.
The problem has been resolved. Actually MVC naming pattern or something else was wrong. I didn't properly renamed my existing component that I was reusing.
I'm using ABCPdf to convert HTML to a PDF. I'm using the method:
AddImageUrl()
This works fine in Dev and UAT, but on Production I continuously get the message:
Unable to render HTML. Unable to load
page
Anyone see this before? Need more info?
-Ev
I guess you are tying to do URL->pdf generation. It is difficult to directly to do URL->pdf conversion. We ended up URL-Save HTML in local folder ->read HTML and convert to PDF-> delete HTML file from folder - tricky approach but it works. The only flaw is that you need to give read/write permission on a folder on server. Its still better than decreasing security settings.
have you take a look at this http://www.itjungles.com/dotnet/abc2pdf-unable-to-render-html
The default timeout for abcpdf is 15 seconds. If the page is taking longer than 15 seconds, you will get this exception.
Add the line below just after object creation of the document to resolve the issue.
theDoc.XHtmlOptions.Timeout = 10000000;
I found by working backwards (removing elements) from a target html page that omitting the tag (of all things) created this error. also, calling localhost in the target url generated this error.
I have no idea what caused this error, but I stopped the scheduled task that was running, then restarted it and it's worked fnie ever since.