Community @ The Turning Gate

Well, that is the nature of frameworks. And frankly, WordPress is a bit of a mess in that regard. WordPress itself is one framework layer, and then nearly ever theme for WordPress adds an additional framework layer different from every other WordPress theme. Building Chado was somewhat dreadful, and I am not really looking forward to working on the CE3/Chado2 theme, though it will need to be done.

But really, I am sworn off of "normal drop-down" menus on any kind of touch interface. They're too inconsistent. At least when the parent item is both an active hyperlink and the drop-menu trigger. Not a big deal if the parent isn't hyperlinked. This was probably the largest deciding factor in how I ended up handling navigation for CE3. On touch screens, I think it imperative that parent items not pull double-duty as both hyperlink and drop-trigger.

For now, CE3 purchases include the older CE2 versions mostly for the sake of users still depending on CE2 Cart to power e-commerce galleries. This will be the case until we are able to release a CE3 version cart.

If you have no reason to use CE2 Pages, then you don't need to install it. Stick to the CE3 versions.

Don't use Lightroom's Upload. Export to desktop, then upload using an FTP client. Lightroom's upload is unreliable.

Use ttg_head_end to put in your new styles/stylesheet.

Are there spaces in your gallery folder names? If so, no spaces.

Just set the background colors separately. Keep in mind, though, that those items are layered on top of whatever you're doing to #body-core. So, for example, if I wanted everything to appear the same, rather than piling up my colors, I could do this:

#body-core {
    background-color: #ffffff;
    background-color: rgba( 255, 255, 255, 0.75 );
    }

#social-networking-block .mantle, 
#footer .mantle {
    background-color: transparent;
    }

The templates are named to indicate for which .lrwebengine they are intended. For example, "CE3 Asphalt - Gallery" is for CE3 Gallery. If you have not installed the appropriate web engine, then you cannot use the corresponding template.

Icons in the menu may not work. At least, not when using drop-menus. They interfere with our Javascript for the carets.

Within the traditional context of exported-and-uploaded web galleries, breadcrumbs simply will not work. They would require the user to know and hardcode the entire breadcrumb trail for each individual gallery. Hello, Nightmare.

Using Publisher, we have a consolidated architecture from which to draw the gallery structure. By which I mean that breadcrumbs are a possibility for publisher galleries, whereas they have not previously been a feature that we could hope to implement in any meaningful or sane way.

That said, it's not something we expect that you should be able to do using PHPlugins. It's something that Ben will need to work on for a publisher update and would fall under the heading of "publisher enhanced" gallery features. We've talked about it before, but it just hasn't happened yet, as we've had other priorities like getting CE3 out the door, and Ben making publisher tweaks to help make that happen. At this point, he would need to chime in on his schedule of priorities for upcoming releases.

No reason at all, though I would keep them around in a backup location rather than outright deleting them. I'm also a digital packrat, though, so take that for whatever you think it's worth ...

I only keep the CE2 plugins installed for support reasons, and I uninstalled the early versions ages ago.

When you say "header text", what are you talking about?

It works "fine" everywhere. It's just a matter of how the browser maker wants to implement their scrollbars. Safari still has scrollbars, you just have to know how to use them. I grab scrollbars all the time in Safari.