Gantry 4: Am I missing something? can't click anything
-
-
- LiEs
- Sr. Rocketeer
- Posts: 238
- Thanks: 0
-
I installed the bundle with new joomla 2.5.6 install on xampp 1.7.7. I make gantry default. Then I try to click on tabs and nothing happens. I try to close template to go back to Joomla Cpanel, but that doesn't work either. I tried with chrome and firefox. Then I tried rocketlauncher, and same thing. I cleared browser cache.
:: php 5.3.8
:: Joomla 2.5 - Last Edit: 12 years 8 months ago by LiEs.
-
-
-
- webarnes
- Sr. Rocketeer
- Posts: 107
- Thanks: 6
-
I installed the Gantry 4 RL yesterday morning and went smooth.
Works great.
Are you referring to front end links or administrator template links that will not click?
You refer to Joomla cPanel but the Joomla Administrator and your server cPanel are two different administration panels.
can you post the url that this is happening on?
Did you start a fresh install on a clean directory?
New database?
Regards,
William - -- William
-
-
-
- LiEs
- Sr. Rocketeer
- Posts: 238
- Thanks: 0
-
webarnes wrote:
I installed the Gantry 4 RL yesterday morning and went smooth.
Works great.
Are you referring to front end links or administrator template links that will not click?
You refer to Joomla cPanel but the Joomla Administrator and your server cPanel are two different administration panels.
can you post the url that this is happening on?
Did you start a fresh install on a clean directory?
New database?
Regards,
William
This is my local pc. fresh install. when I edit gantry template in the back-end all the template links do not work (save,prests,clear cache,close,all tabs). this is what firebug show
Scroller.init is not a function (?)()index....it&id=9 (line 109) fireEvent(f=function())mootools-core.js (line 375) forEach(i=function(), v=Window index.php? option=com_gantry&view=template&layout=edit&id=9)mootools-core.js (line 40) fireEvent(e="domready", c=[], b=undefined)mootools-core.js (line 375) g()mootools-core.js (line 514) Scroller.init('presets');
UPDATE: I installed framework and template separately and that worked for me.
-
-
-
- Greg Podesta
- Rocketeer
- Posts: 58
- Thanks: 1
-
I have the same problem, but have a great deal of time invested in the template setup, only to discover it doesn't work on our production server.
What's the best way to back out of this and as mentioned above, install the framework, then the template separately, but to be able to restore my settings. Is it as simple as restoring what is in the #__template_styles table?
-
Time to create page: 0.075 seconds