Forum Replies Created
-
Posts
-
Sounds good @Susan - Thanks!
Ah yes, the FAQs... I did look there, originally. However, right below, the box, where we all compose these forum posts, it says:
You may use these HTML tags and attributes:
The code element is shown a little differently than the FAQs... So, when someone is writing, and wonders how to do something, on the fly, and see that list of HTML tags and attributes, it leads to confusion.
@rbrown08 - I'm not sure what version of IE you are using, but I've not had a problem with IE and iFrames, for a while. As best as I can remember, iFrames have worked with IE, all the way back to at least 2005. I know there have been some issues reported, but of the issues I'm aware of, just about all of them were due to restrictive settings in IE, which I don't think can be avoided, even today. Similar to disabling JavaScript, if iFrames are not allowed, they wont work.
That being said, @tomarob I'm not sure iFrame-ing is a good idea for a flash movie, or any media object for that matter.
The HTML iFrame Element (or HTML inline frame element) represents a nested browsing context, effectively embedding another HTML page into the current page. - Mozilla
While I'm sure there is a way to use iFrames, displaying a Flash video on a page, does not require access to another HTML Page. The Flash .SWF file simply needs to be embedded. This can be done by uploading the Flash .SWF file, in the WordPress Media Manager and using the .SWF file's path (URL) to embed it with the traditional Flash embed script.
In the end, I usually recommend against using Flash on a website's home page or on priority landing pages. There are so many things which can keep Flash from working correctly, if at all.
In the case of my client, their old website was built entirely in Flash. The client wanted to embed the old Flash website (one .SWF file) on a single page, so it was accessible by those who want to continue using it. The main home page though, was not ever going to contain an embedded flash video. The home page would have had two links on it - one for the old flash website and one for the new website.
@ron rennick - thanks for your input. Your solution does work, as I have done, exactly that on one website. I came up with that idea, about a week ago, when trying to find a temporary work around for this issue.
Again though, your response amplifies the problem. StudioPress/Genesis released the Outreach Child theme, with a built-in problem. No one wants to jump through a whole bunch of hoops, to use a theme they had to pay for. It should just work.
@deckerweb - No, I haven't submitted a support ticket through WordPress.org yet. If you haven't done that already, I'd be happy to go ahead and submit the ticket.
I started with this forum, as the Plugin is required for full functionality of Genesis' Outreach Child Theme and it is one of the "LISTED" plugins, found on the StudioPress website (http://www.studiopress.com/plugins/genesis-responsive-slider). I know there are plenty of plugins for Genesis, which are not developed by StudioPress, but for me, if a plugin is used in an "OFFICIALLY" supported child theme, the plugin, itself should have been verified to work.
An unofficial Genesis plugin, should never be part of an "OFFICIALLY" supported child theme, for this exact reason. Either build the functionality, directly into the theme and provide support for the whole thing, or use the plugin, but provide support for both the theme and the plugin.
Oh, and FYI: The "Responsive Slider" doesn't seem to be that responsive, either.
Ok, ok, I'll get off my soap box!
Now, I have a recommendation on how to fix this...
Allow the developer to define the specific order, by ID, instead of using a pre-defined “ascending” or “descending” option. Let me create a list, separated by commas, showing the IDs of the pages/posts, in the exact order I want them to occur.
While I appreciate the responses, so far, your answers only amplify the problem. StudioPress/Genesis is releasing themes with built-in problems and charging people for them.
Not only has the Genesis Responsive Slider not been updated since last year, but it hasn't been updated since the latest release of Genesis. Then, on top of this, there is an issue with the functionality of the slider, in that the methods provided, to organize the display of the images, don't work.
If StudioPress/Genesis is going to make themes available, for sale, which require other plugins, for full functionality, the plugin should be required to be as up to date as Genesis and the Child Theme.
FYI: Forum Admins and Moderators, the CODE tag isn't working correctly! When the CODE tag is being used, some HTML is still being rendered instead of printed to the screen, as you can see above!
Also, the option to edit posts goes away after a specific amount of time, right? Well, if you use your browser's BACK BUTTON, you can edit the post as many times as you want, even without the presence of the BACK BUTTON - as I'm doing now.
So, here is what I've put together, based of the afore mentioned articles/tutorials:
<?php
/**
* This file adds the Landing template to the BamajrEFM Child Theme.
*
* @author Bamajr
* @package BamajrEFM
* @subpackage Customizations
*/
// Add custom body class to the head
add_filter( 'body_class', 'add_body_class' );
function add_body_class( $classes ) {
$classes[] = 'bamajrnhcc-splash';
return $classes;
}
// Remove header, navigation, breadcrumbs, footer widgets, footer
add_filter( 'genesis_pre_get_option_site_layout', '__genesis_return_full_width_content' );
remove_action( 'genesis_header', 'genesis_header_markup_open', 5 );
remove_action( 'genesis_header', 'genesis_do_header' );
remove_action( 'genesis_header', 'genesis_header_markup_close', 15 );
remove_action( 'genesis_after_header', 'genesis_do_nav' );
remove_action( 'genesis_after_header', 'genesis_do_subnav', 15 );
remove_action( 'genesis_before_content_sidebar_wrap', 'genesis_do_breadcrumbs');
remove_action( 'genesis_before_footer', 'genesis_footer_widget_areas' );
remove_action( 'genesis_footer', 'genesis_footer_markup_open', 5 );
remove_action( 'genesis_footer', 'genesis_do_footer' );
remove_action( 'genesis_footer', 'genesis_footer_markup_close', 15 );
genesis();
It produces a white box with the generic first post in it, which I do not want on the home page.
At what point do I add the suggested HTML?
I realize I need to add something similar to:
Old Flash Site Enter New Website
But, I guess I'm unsure of where to add this, in the code I've shown, above. I need to ensure blog posts are not part of this page.
Ok Nick,
If it happens again, I'll let you know.
I'm still a little curious though, as to how Akismet marked me as a spammer. I write for and comment on several blogs, using Akismet and that same email address. None of my work on those pages has been flagged as spam, so it's not like Akismet has blacklisted my email address.
Thanks for your response Chris...
I must be doing something, little or big, wrong. This is exactly what I've been doing and I'm not quite getting what I want. I'm going to look over my work again to see if I can find what ever it is I'm missing.
I don't want to salt an old wound, but I think there splash pages and landing pages are completely different.
For most website designers, wouldn't a splash page only be found at the root of the website (I.E. http://bamajr.com/ not http://bamajr.com/landing-page/)? Also, aren't most splash pages limited to a single embed of flash, an image, an image slider or video, with very little or no text?
I'm bringing this up because I'm having a hard time creating a "splash page" using the home.php file, but I've created many landing pages, using Brian Gardner's "How to create a Landing Page" process.
Here's the issue. I have a single image. Lets say it is 800px by 600 px. I want to include this image, a button, below the image and contact information on a line below the button. I do not want anything else on the page (I.E. No header, navigation, blog posts, sidebar, sidebar widgets, footer widgets or footer).
This is rather easy, when creating a basic PHP/HTML website, but not as easy when using WordPress/Genesis. Am I missing something here that is making this too hard?
I think the
<code>rel=author</code>
...is old news, which Yoast's plugin already resolves, for those who cant figure out how to add it to their theme, another way.
I'm more interested in issues related to the:
<code>Warning: Missing required field "updated".
Warning: Missing required hCard "author".</code>...errors which continue to occur for people using Genesis, which have not been addressed by Yoast's plugin. These errors are not related to the rel=author tag. So I'm curious if this will be fixed, out of the box, with Genesis 1.9
