Community @ The Turning Gate

Nope, still happens. It's happening less often but not fixed.

It's obvious when it happens because the top of my background image is more light than the bottom. When the scaling bug happens, the background jumps from light to dark when scrolling down, and then dark to light when scrolling up.

BTW - because my background image isn't uniform, I can't use repeat to create a tile effect.

That said, I just realized I can make it less obvious by having a similar brightness across the entire image. The subtle randomness of the background will mostly go unnoticed when it moves, but at least it wrong jump up and down in brightness.

I've added {background-attachment: scroll} to my CSS. I haven't seen any bad side effects, but I'm still seeing the background jump. It happens while scrolling in portrait mode. It seems to be better (fixed?) while in landscape.

The behavior seems to be scrolling is causing the background image to be scaled wider. I'm guessing the viewport is getting changed causing the background to scale wider, making it look like the background has jumped.

Interesting to note that in the wider landscape mode it's not being re-scaled while scrolling. Seems to be linked to the narrow width of portrait mode.

I couldn't find how to monitor the viewport, which I suspect it getting changed during scrolling. I've spent too much time looking at this. I've found it's been an iOS bug forever, across every release from Apple. Makes me sad to see such an obvious glitch in Apple's visual design.

I haven't coded with jQuery before, and only read a few things to get me started. After some hacking I found the code below is working. That is, it highlights the currently selected sub-menu under Photos and then the parent menu Photos.

The <current_page_item> class is being added to the <a tag>.

I'd much prefer the  <current_page_item> class was added to <li> tag. Then it would match the behavior of WordPress, and my CSS would be consistent.

After continuing to hack away, I'm not getting any closer.

BTW One of the odd things I can't explain is how <current_page_item> is added to the parent menu when the sub-menu is selected. I suspect that's another clue to my problem.

Menu structure created by Backlight

<ul class="primary-menu menu mouseable">
<li class="menu-item"><a href="/">Home</a></li>
...
<li class="menu-item menu-item-has-children"><a href="/photos/">Photography</a>
<ul class="sub-menu">
   <li class="menu-item"><a href="/photos/01-slug/">Item A</a></li>
   <li class="menu-item"><a href="/photos/03-slug/">Item B</a></li>
   <li class="menu-item"><a href="/photos/04-slug/">Item C</a></li>
   <li class="menu-item"><a href="/photos/about-my-photography/">About</a></li>
 </ul>
 </li>
</ul>

Script added to PHP Plugins

function ttg_scripts( $style, $path ) {

echo <<<SCRIPT
	<script>
		$(function() {
$("ul.menu a[href='" + window.location.pathname + "']").parentsUntil('menu-item-has-children').children('a').addClass('current_page_item');
		});
	</script>
SCRIPT;

} // END

Even brute force doesn't seem to do the trick. I added this to my child theme's functions.php

add_filter( 'wp_default_editor', create_function('', 'return "tinymce";'), 1 );

I was thinking I could remove the builtin filter, but Backlight adds the filter without using a function name so I can't remove it. I can alter the original code in the parent theme, and that works until I update a template. Since I'm in the middle of creating the theme it's getting instantly overwritten.

Without understanding it, I can verify that there is something in the .htaccess file that's causing the 404. I simply renamed it, and reloaded the page. Then the URL works. I should have thought to test that in the first place.

At least I know where to look next. I'll guess it's going to be some assumption by the hosting server "knowing" where WordPress files are, and preventing access to other areas.

Then again, on second thought, does Backlight install/modify the .htaccess file within the galleries directory?

BTW - Backlight is turning out to be awesome. I've been using TTG plugins since the very first release. I put off upgrading to Backlight until I moved my site to a new hosting service. I also added SSL and the new sever includes a more rigorous .htaccess.

That's what I would have expected. In my page template I use only within Backlight, I added the identifier "photo-page" and in the CSS I find the class <template-identifier-photo-page> for all pages associated with that template.

I have a cloned page template with minor differences I use for the Wordpress theme. This is the page template associated with the Wordpress theme add-on. It exports into Wordpress and everything seems fine, except for the missing identifier.

In that Wordpress page template I added the identifier "wordpress-page". When that gets exported into the Wordpress theme, it loses the identifier. Seems that the identifier is ignore when exporting a page template to Wordpress.

Examining the Home page the BODY tag contains only the following:

<home page-template-default page page-id-11 logged-in pangolin type-theme slug-backlight-theme>

The other pages created by Wordpress are the same, minus the "home" class.

I would have expected to find <template-identifier-wordpress-page> in the BODY of each page created by WordPress. Maybe exported page templates are not suppose to include the identifier. It seems like a bug, so I wanted to report this.

Still, I found I can use the <slug-backlight-theme> class for CSS overrides that are specific to WordPress pages.

I'll add your change and see how it works, then let you know.

I understand your intent of always using the text editor. I think people using WordPress are used to how it normally behaves. A change in the behavior just shows up as "broken."

If you didn't alter the behavior, it works for you since WP will "remember" your preference.

I use both the visual and the text editor. It also works for me since I'm always jumping back and forth, and I'm expecting it to be how it was last time. I even go the extra mile and customize the WP admin css so my visual editor looks close to the actual page.

I'm not clear what this means, but it sounds like Backlight is not an option for me. I need to add my photo gallaries to my existing WordPress site. I did this using the PHP Plugins to add my site's navigation and custom CSS so the TTG's look matched.

How can stand-alone albums "fit right in" if I can't have my sites existing menus/navigation integrated?

Today I have my WordPress site include a menu for Photos. That page is generated by the TTG Plugins. I have TTG navigation and header disabled. The TTG Plugins simply generate the pages content, within a simple wrapper I created using the PHP Plugin.

Are you saying this isn't possible? Sounds like you're saying Blacklight creates it's own navigation menus, and going from my existing site to the Blacklight page would be like going to a different web site.

Any more details on how to integrate Backlight with an existing WordPress site?