Akeeba Backup and a Development Site
-
-
- JEM
- Preeminent Rocketeer
- Posts: 17917
- Thanks: 4
-
Getting Fast Support: Akeeba Backup and a Development Site
If you haven’t followed the guidelines posted here, www.rockettheme.com/forum/index.php?f=15&t=36997&rb_v=viewtopic , after posting a question you've probably seen something like this from one of the moderators or another member.
JEM wrote:Could you please provide a link to your site in this thread, and if applicable, a direct URL to the issue?
If you are on a local install, or prefer not to post a link, you can use FireFox and FireBug, a free debugging tool to inspect your site.
You could also attach ( using Upload attachment below this text field ) a screen shot of the issue you are facing, and if applicable, provide annotations.
While screen shots are helpful, we can’t use debugging tools on them to suggest changes to achieve the desired results so posting a link to a live site where the problem exists is your best option.
Of course, just posting a link is fine but for the members that hesitate for the reasons listed below...
If you'd like a really fast resolution to your issue, I suggest using Akeeba Backup, backing up your local install or your current site and then making it live on a development site we can have access to.
www.akeebabackup.com/akeeba-backup-for-joomla/index.html
You can install it in a subdomain or simply put it in a folder on one of your domains, i.e., create a folder called 'dev' or 'test' run the installer, then provide a link.
Hopefully, replies like these will be fewer and the turnaround time for you support request will be faster.
‘It’s on localhost.’
See above.
‘It’s currently offline.’
‘It’s under development.’
‘It’s not ready to be live.’
It needs to be accessible, this requires posting a link, preferably in the forum, as it’s the main support vehicle for RT. If a moderator sees your issue and thinks they can solve it, they usually ask for details in a PM. Especially without posting in the forum first, you should try to refrain from sending random PMs to moderators unless asked to do so for the following reasons:
A) Not every moderator knows the answer to every question.
All members can benefit from the answers you receive.
C) If moderators are ‘forced’ to resort to support through PMs, while they are answering via PM, other problems posted on the forum, perhaps even yours, go unanswered.
‘I don’t want search engines pick up the URL.’
A general rule of thumb, don’t do your development on the URL the final site will reside on. Use a development site, provide a URL, and when everything is perfect, move it to its final destination.
‘Here’s a link, but I had to unpublish the (Article / Module / Menu / Component) because it (looked awful / page wouldn’t load properly / broke the layout of the site).’
If you’re going to provide a link you’ll have to have a link to a live site where the problem exists so whoever is going to assist you can take a look. We can't fix what we can't see.
If your site is already live and you can’t leave the (Article / Module / Menu / Component) module published for what ever reason, create a development site.
In the development site, you can leave the (Article / Module / Menu / Component) published, and allow us to look at the site live with the issue you are facing.
When you get it sorted on the development site, you can make the changes on the live site. - Thanks,
jim
-
-
-
- Paulo Roberto Santos
- Sr. Rocketeer
- Posts: 192
- Thanks: 0
-
Hi, its here you suggest to post this topic?
www.rockettheme.com/forum/index.php?f=20...73276&rb_v=viewtopic
-
-
-
- JEM
- Preeminent Rocketeer
- Posts: 17917
- Thanks: 4
-
Paulo Roberto Santos wrote:
Hi, its here you suggest to post this topic?
www.rockettheme.com/forum/index.php?f=20...73276&rb_v=viewtopic
No, I was referring to your reply in your thread.
Paulo Roberto Santos wrote:Jem,
this is the RokAjaxSearch published with search options disable.
Regards.
If the search options are disabled on your site, we cant inspect the site with debugging tools to suggest the css changes you need to make.
If you don't want to enable them on your live site, I suggest setting up a development site, as stated above:
If you’re going to provide a link you’ll have to have a link to a live site where the problem exists so whoever is going to assist you can take a look. We can't fix what we can't see.
If your site is already live and you can’t leave the (Article / Module / Menu / Component) module published for what ever reason, create a development site.
In the development site, you can leave the (Article / Module / Menu / Component) published, and allow us to look at the site live with the issue you are facing.
When you get it sorted on the development site, you can make the changes on the live site. - Thanks,
jim
-
Time to create page: 0.053 seconds