How to get Help QUICKER!
-
-
- DanG
- Preeminent Rocketeer
- Posts: 36750
- Thanks: 3229
- Custom work done
-
1.
If this is a site that is online could you please supply a link so we can better diagnose the issue?
It makes our suggestions more accurate if we see the actual coding of your site.
If it requires privacy, only then contact us by PM.
-
-
-
- DanG
- Preeminent Rocketeer
- Posts: 36750
- Thanks: 3229
- Custom work done
-
2.
DO NOT send PM's to Moderators unless requested to do so. If we need your info, please use this format:
- your thread link
- website URL
- UserName and Password for Admin access
- and if required FTP login details.
-
-
-
- DanG
- Preeminent Rocketeer
- Posts: 36750
- Thanks: 3229
- Custom work done
-
3.
Save time and money. Copy this to your post and your on your way to helping yourself to get your issue resolved QUICKER!
- My website URL is: http://www.mysite.com - My Joomla version number is J-x.x.x - My Rockettheme template version number is: x.x.x or - My RocketLauncher version number is: x.x.x or - My Rok-extension version number is: x.x.x running on template [u]rt_template-name[/u] - My Gantry version number is x.x.xx My issue is: -
-
-
-
- DanG
- Preeminent Rocketeer
- Posts: 36750
- Thanks: 3229
- Custom work done
-
4.
NEVER have caching or compression turned ON while developing, because:
a) you can always test to see if these processes work early on after install but turn them OFF while actually developing. Otherwise you'll find yourself making changes in the back-end but not seeing them in the front-end.
After development and during debugging before going live you can turn them back on again.
b) it makes it much harder for us to help you when caching and compression is ON. We can't see the contents of your cache and we have no clue what CSS file css-62772285f72c78f6d865166b5edd82f6.php refers to ???
-
-
-
- DanG
- Preeminent Rocketeer
- Posts: 36750
- Thanks: 3229
- Custom work done
-
5.
This image is hidden for guests.
Please log in or register to see it.
Once your issue is resolved, PLEASE! mark your FIRST POST in the TOPIC as
[SOLVED].
This makes it so much easier to find and address other members issues and those of yours.
-
-
-
- DanG
- Preeminent Rocketeer
- Posts: 36750
- Thanks: 3229
- Custom work done
-
7.
Get used to using an Inspector Tool like Chrome Developer Tools - Last Edit: 9 years 8 months ago by DanG.
-
-
-
- DanG
- Preeminent Rocketeer
- Posts: 36750
- Thanks: 3229
- Custom work done
-
8.
After making changes ALWAYS clear your Admin caches and your Front-End browser cache.
......................................................LIFE
.............................................................|
....................................____________
..................................|............................|
..............................GOOD.......................................BAD
.........................trouser cash..........................browser cache - Last Edit: 9 years 8 months ago by DanG.
-
-
-
- DanG
- Preeminent Rocketeer
- Posts: 36750
- Thanks: 3229
- Custom work done
-
DanG wrote:
4.
NEVER have caching or compression turned ON while developing, because:
a) you can always test to see if these processes work early on after install but turn them OFF while actually developing. Otherwise you'll find yourself making changes in the back-end but not seeing them in the front-end.
After development and during debugging before going live you can turn them back on again.
b) it makes it much harder for us to help you when caching and compression is ON. We can't see the contents of your cache and we have no clue what CSS file css-62772285f72c78f6d865166b5edd82f6.php refers to ???
For an excellent explanation of caching systems see this article by Andy -> Caching EXPLAINED
-
Time to create page: 0.070 seconds