There is simply no need to do this. As @Bakual has already said, your approach is bad practice.
For starters, you are wrapping a function within a function unnecessarily when it's not required. You are then returning JFactory::getDocument()->countModules(...), meaning you are calling the JFactory class, then calling JDocument which has to check if it ...
Some links that might be of help:
Template Considerations during Migration
Converting previous Joomla templates
Migrating a template from J1.5 to J3
StackOverflow - converting a J2.5 to J3 template
and you can probably find a lot more resources if you do a web search.
The process of converting a Joomla 2.5 template into 3.4 is removing deprecated and removed functions.
It's more difficult if the template has older legacy functions from Joomla 1.6, and 1.7.
Here is a reference that could help
The solution for this question is as follows:
One needs to add a new file at the location below, to add a custom jdoc tag..
File name should be same as the tag you are adding.. suppose one wants to use scripts as tag then file name should be scripts.php
Now in this file one needs to add a code like below. As tag ...
I think I wanted to do something like this, i.e., extend Joomla class, using plugins. I decided not to pursue the idea but I did find the article "Extending Joomla! With Plugins" helpful.
If it helps great. If not, Oh Well.
Thought I'd expand on my comment.
You're firstly going to need to add an install-uninstall-update script file to your component. Have a read of the Joomla Documentation on how to do this.
Once you have implemented this, you're going to want to use the update function which will only execute this code when the user is updating the component.
Inside this ...
I use StarAzure.com themes that are also based on Warp 7. I had the same issue and one of the following solved this for me - Thanks to a great support policy that StarAzure has.
Make sure that your styles folder and the template folder has proper permissions - write permissions should be available because saving and/or adding a new style in the customizer ...
This allows you to build pages and each one can be different. For example, page specific modules, permissions, styling, and so on.
Page builders focus more on the structure and content of the page.
The template is the overall design of your site so it's more generic and will normally apply any changes you make globally. ...
The alerts derive from Bootstrap, therefore when developing a custom template, you need to make sure you include Bootstrap, and of course, jQuery.
You can do so by adding the following lines to your template's index.php file:
I think it is an interesting question and I've got to this point earlier myself during developing an extension. I do not think there is any strict solution on this but there is a workable approach which comes from the structure of Joomla and I only would like to share that approach here.
First of all, you are a very kind person if you want to provide more ...
Simple answer. Don't bother.
You'll spend a lot more time attempting that than either finding a similar looking Joomla 3 template and customising it or just creating a new one yourself. Joomla 3 templates are now designed as responsive and have left behind many deprecated functions from 2.5.
There are both a free and a commercial version and you can compare their features here: https://www.jch-optimize.net/downloads.html
It occurs to me that running two different versions of jQuery on the same site will give you a lot of headaches, and a lot of coding challenges unless you're a very experienced coder.
A quick Google search revealed that it might be possible to use jQuery 1.7 with VM:
If your template uses bootstrap.js then to solve a script error with
The best way might be to write a plugin and use the right events:
The context would be "com_templates.style".
public function onExtensionAfterSave($context, &$templateTableStyle, $isNew = 0)
if(com_templates.style == 'com_templates_style')
// do your work ...