Hi Ash
Thanks, I did get around it when I found out you only had to disable it on pages, posts, categories, tags, custom posts and 404 pages. After that the other modules seem to work the opposite way. They don't expect to need you to disable them as I guess they are a subset of one of the above.
Did you get anywhere with the display on page templates option? I really think that will be a useful addition.
Cheers
Simon

Hi Adam,
I ended up using Snapshot to copy files and database across. That worked reasonably well.
You might be a bit early releasing shipper at the moment as there must be a lot of plugins that use AWS SDK. I have tried it on quite a few sites and haven't got any to work so far. At the moment Snapshot import seems more reliable.
I should also add that it is very, very slow. I know this is because you do things file by file, but maybe you could reduce this a bit to only files that need this. You could for example zip plugins individually and send.
Actually, one last feature request for when it is ready. I would love to see a schedule system in there too. I have a couple of sites that I have to sync weekly. I was doing that with Wordpress export, but I've just realised that only adds and doesn't update.
Thanks
Simon

I am looking at Shipper too but not for backup. That fails too I'm afraid. I have to say that Shipper, the easy migration tool, hasn't yet successfully run on any of the sites I have tried it on. Not exactly the must have tool I was hoping for!
As for the Snapshot install. All the files are there and correct, just no manifest. I have updated Snapshot and am still seeing the same results.
This site is very locked down (Bitnami on Amazon) including no access to wp-config.php and no FTP. So I'm stuck on that one I'm afraid.
Any other ideas?

Hi Adam,
Yes I agree. This would be a really nice feature to add. Having to do it manually like I did was a bit of a pain and you really wouldn't want to be controlling your trigger and your hustle slidein separately. You can just imagine what a mess clients would get into with that sort of arrangement.
Cheers
Simon

Hi Predrag,
Unfortunately not, adding display:block into the theme template code did show the tab I had built, which then opened the contact form, but the #hustle-trigger-wrapper div then stayed open over the top of the page, which meant you couldn't click on anything.
What I have just done, which seems to solve it, is add some size information into the inline css for that div too. I now have: -
<span class="wph-modal module_id_2" id="hustle-trigger-wrapper" style="display:block;height:20px;width:200px;left:-2000px;">
<?php echo do_shortcode("[wd_hustle id='contact-trigger' type='slidein']Can't find what you're after?[/wd_hustle]");?>
</span>
I sized the containing div to match the tab, but as the tab itself has a fixed position, I was able to move the container way off the page (left:-2000px), just in case it got in the way of anything.
Seems to be working now thankfully! It might be good to build this feature in as I bet if I was looking for it, other people will be too and it's not easy to create a proper tab without a lot of scripting, which I didn't want to do, as it then gets too hard for clients to edit.
Cheers
Simon

Just realised that this relates to an earlier help request. The solution I came up was to add display:block to an element which is what is causing the problem. I'll have to look at this more closely to try and trigger it another way.

Hi Adam,
Thanks... I can't believe I missed the first part of that selector!
As it happens, the surrounding span in your code above is also hidden by default, but it was easy to just unhide that in the span. The working code therefore ended up: -
<span class="wph-modal module_id_2" id="hustle-trigger-wrapper" style="display:block;">
<?php echo do_shortcode("[wd_hustle id='contact-trigger' type='slidein']Can't find what you're after?[/wd_hustle]");?>
</span>
Other things I found is that this system uses Gravity forms, but the default AJAX confirmation is never seen as the modal closes (but the wrapper doesn't, which prevents clicks on the page). To get around this I just sent the confirmation to a page rather than using AJAX.
Thanks for your help.
Cheers
Simon