Component - Code
Component - Comments
Component - Editor
Plugin - Search
If you are getting this error when trying to install, it usually means that a previous install of JaggyBlog was made and there is data partially left over, stopping it from installing again.
To resolve the issue delete these jaggyblog database tables and try again:
If you get an error like "Parse error: syntax error, unexpected $end in /home/(site name)/public_html/administrator/components/com_jaggyblog/views/cpanel/view.html.php on line 1". This usually means that you did a site transfer and one or more JaggyBlog files got corrupted. Please redownload and reinstall the component and any modules to resolve the issue.
The main point to be aware of when updating to Joomla 2.5 is that JaggyBlog's blog posts are merely articles stored in Joomla, so these are not lost on an upgrade, as long as the required Joomla based database tables are transferred across.
The JaggyBlog database tables that need to be transferred are the ones that store the blog tags and comments posted, unless of course you are using another form of comment submission like Facebook or JComments.
Apart from this, as long as the required database tables are exported and imported correctly, the only task needed to get JaggyBlog functioning when upgrading to Joomla 2.5 is to make sure you install the latest version of JaggyBlog and set it up again via its configuration screen.
Edit the following file via FTP: "/language/en-GB/en-GB.com_jaggyblog.ini". This is the language file that stores all of the editable text used within the frontend of the JaggyBlog component.
If you enabled captcha but the image is not displaying, this usually means that JaggyBlog does not have enough file permissions to use the PHP file that generates the image via "/components/com_jaggyblog/assets/libraries/captcha/index.php". Make sure this file has group/owner permissions via FTP to read and execute. If this doesn't work, this means that your web server does not have the "GD image library" server module enabled, which lets PHP dynamically generate images. This means that you will need to contact your webhost and enquire about enabling it. Also mention the URL for the file above, as they may be able to help you specifically with getting that file to work.
If after posting a comment, the comment area goes blank and the comment doesn't submit, it is likely to be because of this error:Warning: file_get_contents(/components/com_jaggyblog/assets/templates/universal/ajaxcomment.php) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.0 401 Authorization Required. The first possible fix for this is to go to line 78 in the file at "/components/com_jaggyblog/jaggyblog.php" via FTP and change "true" to "false": $jaggyxajax->configure('deferScriptGeneration', true);
The second reason why posting comments might not work is due to the security on your webhost. Sometimes a software firewall called "mod security" is installed that stops certain web functionality from working. You may need to contact your webhost and send them the error message above so they can enable the file mentioned.
JaggyBlog supports all the same plugins that normal articles do in Joomla, so using a plugin like All Videos will work in blog posts.
While creating or editing a blog post in the front or backend. Underneath the editor should be a "read more" button. This allows you to insert a line that sets where the blog post should be cut off and where a "read more" link appears. This link can then be clicked to access the full content of the blog post.
While using Joomla's search module with JaggyBlog's search plugin, if you run a search that displays a JaggyBlog post twice, this is because Joomla as a default returns the "com_content" based articles and the "com_jaggyblog" based articles, on top of JaggyBlog's search plugin returning "com_jaggyblog" articles!
To stop this from happening, the "com_content" search plugin needs to be updated to tell it not to search for "com_jaggyblog" based articles, and just leave it to the JaggyBlog search plugin to display them. Copy and paste the code from the file here (search-plugin-01.txt) and overwite all the code with it located in your website file at "/plugins/search/content/content.php".
Making your own JaggyBlog template is very easy, using Joomla's default method called "template override". To help you do this, download the pre-made template override files for JaggyBlog (jaggyblog_template_override.zip). Once downloaded, extract the folder to the site location:
"/templates/(name of site template you're using)/html/"
Once extracted, you should have the folder structure:
"/templates/(name of site template you're using)/html/com_jaggyblog/jaggyblog/"
Inside the last folder of that location, you should have 7 php files, each representing a layout in JaggyBlog for you to edit (such as default.php). Now this is done, go into JaggyBlog's Configuration Screen and save the blog template option called "Custom".
With this done, you can now edit any of the php files to what layout you want. You can also style any of these layouts by using the style-sheet in the template override folder at:
"/templates/(name of site template you're using)/html/com_jaggyblog/jaggyblog/css/custom.css".
Regarding the design of JaggyBlog, at the moment the admin area provides two templates to choose from, "Universal" and "Gradient Beige". The gradient one simply adds a beige, gradient background to each blog post listed out, as shown in the demo.
Any other styling beyond this is determined by the site template you are using, this is where the "Universal" template option in JaggyBlog comes in handy. What this does is make the design plain, without the beige background.
The Universal option picks up as much styling as possible from the site template you are using. For example, on the JaggyBlog demo, it shows a silver looking module for "Blog Categories". This is done via the site template I have installed, not JaggyBlog. Any styling for modules and fonts etc are determined by your site template and will need to be adjusted accordingly in the style-sheets for your site template.