Community @ The Turning Gate

Regarding what? ·?

You can't do it using Markdown syntax, but Markdown also allows you to write regular HTML, so do that for the links.

I've already had a look, and it's a pretty simple fix from my end. Can be done by applying simple math to the value returned from the gradient sliders in Lightroom. The hard part for me is just going to be tracking down all of the gradient controls in each of the plugins and updating accordingly.

The trick is to leave prefixed -border-radius properties as they are, and they will continue to be used by older browser versions not supporting the unprefixed border-radius property.

The larger problem is going to be for users who will need to make this change to their existing pages and galleries, already published to the web. Easier for those already using PHPlugins, who can just put override statements into a custom stylesheet. Not as easy for anyone running pages published in the traditional way ...

For anyone curious, here's the code for the background gradient on the Chado site, http://chado.theturninggate.net:

    background-image: -webkit-linear-gradient(270deg, #DEE877, #FFFFFF 65%);
    background-image: -moz-linear-gradient(270deg, #DEE877, #FFFFFF 65%);
    background-image: -o-linear-gradient(270deg, #DEE877, #FFFFFF 65%);
    background-image: -ms-linear-gradient(270deg, #DEE877, #FFFFFF 65%);
    background-image: linear-gradient(180deg, #DEE877, #FFFFFF 65%);    

Note the values of 270deg for all prefixed properties, and 180deg for the final border-radius property. This is a vertical, top-to-bottom gradient.

For what it's worth, these updates are already applied to all child themes where relevant in the Chado 1.1.1 update. Updates to TTG plugins are more complicated and will take a bit longer.

Apparently, CSS3 Animations, Transitions, Transforms and Gradients have been unprefixed in Firefox 16, and the gradients syntax has changed. I suppose this will warrant updates. And this is what happens when we implement prefixed features in web-design ...

Details here:
https://hacks.mozilla.org/2012/07/aurora-16-is-out/

Hi Giovanni,

Firstly, thank you. I very much appreciate your kind words and your encouragement.

As for search capability, no database = no search. The best you could do is implement a Google search for your site specifically, but I'm not sure that would be the solution for what you want to do. Sadly, nothing else comes to mind.

The alternative would be to run through galleries through a content management system, such as WordPress. But no WordPress theme or plugin that I am aware of would give you client proofing capability, and that would also necessitate that you input keywords for every individual image, which would be a bear of a job.

Q: Why don't you offer refunds?
A: We don't use serial numbers or security measures of any kind. If I offered refunds, people could just buy a license, download the plugins and then request a refund. They'd get their money back and still have a copy of our plugins. Not cool. Plus, The Turning Gate makes every effort to support our products and to help customers successfully see their sites to launch. We stand behind our software 100%, and very rarely actually get requests for refunds.

In this age of digital products, no refund policies are becoming more and more commonplace. See Apple's App Store as a prominent example. I have been debating for sometime over whether to cease offering refunds. We recently had one of those rare instances of a customer wanting a refund. This customer wasted an absurd amount of my time on support, not because of any functional complaint or shortcoming of the products, but simply because they refused to take the time to understand how to use the plugins or to follow my advice. Finally reaching an impasse, I issued the customer a refund and kindly asked them to delete irrecoverably all software from The Turning Gate. Two weeks later, this very same customer contacted me again with questions because they still had not deleted the plugins. This is the straw that broke the camel's back.

For these reasons, all sales are final. Thank you for your understanding.

The older galleries will still appear in the Auto Index.

Did you manage to enable PHPlugins? If so, in the phplugins.php file output with TTG CE2 Pages, you will find two example functions -- one for the traditional menu, one for the drop-down menu.

Enable the function for the traditional menu. Insert dots between each menu item:

<li>&middot;</li>

No video tutorials, but CE2 offers full documentation and there are a bunch of written tutorials as well. See links for Docs and Blog above.

Your verbosity + my short attention span ... it's a problem on both sides of the street. =P

With PHPlugins, best to have them enabled from the beginning. Saves you a lot of time and effort over trying to implement them later. That's one of the catch-22s of our workflow. They're an advanced feature best toyed with after you already have some familiarity with our system, but they're best implemented from the beginning of the workflow (which is when users are still unfamiliar with our system).

And my support request at the Vanilla forums is still sitting in my drafts folder awaiting moderation before it will appear in their forum. Fuck those guys.