Splashify to show just part of a page? (Rather than header/footer and all else within the splash box)?

Go to: admin/config/system/splashify/what

Select: "Display entered text/HTML full screen" from the menu.

In the space provided, enter HTML code that will open your content in a lightbox.

Good luck!

ditcheva: This feature is not a part of Splashify. You could create a simple module that does this. You could just create a page callback that echos out the webform and doesn't return the full html for the page. Then use that url in Splashify.

Maybe for the Drupal 8 version. But I don't want to add any additional features to the D7 module, since hopefully D8 will be launching next year.

Wow!! That's AWESOME!! Great work!

This is really useful! I am going to make a note to add this feature to the 8.x branch. And people who need it with the 7.x branch can see this thread. Thanks for sharing this code.

I'm marking this issue as Postponed. But again, thanks for sharing this code and letting me know about this feature.

There is a difference between not supporting a module and not implementing new features. Adding a feature not only increases the amount of code that needs to be maintained and supported, but it also makes the interface more complex. It is not smart to add every new feature people suggest.

Last year I added quite a few new features to the module, at the request of the community. I don't think it would be wise to continually add new features all the time, mainly for stability reasons. This is not to say that I am not 100% dedicated to the 7.x branch. I'm just at the point where right now adding a feature where a small percentage of the users would use that feature, is not worth it. Now if this turns out to a be a big need from the community, than I'm all for considering adding it in.

With the 8.x branch, I think we need to decide on the core purpose of the module in the beginning, so that we include the main features people would need and have a perspective in deciding when new features should or should not be added. Being able to extend the module for more advanced and custom use cases might be a top priority, for example.

In other words, I do appreciate your passion and what you've done here, but I am only interested in adding new features to the 7.x branch when it is clear it is a big need from the community.

good job

Ok, so my vote is for incorporating this patch into 7.x. Whenever I want to add a splash page, basically as a initial warning of the website, I don't want it to repeat the header again, it looks horrible. I only want the body of the content in the splash. I think this addition is a must, really.

By the way, ditcheva, I got the patch and executed against stable which returned an error. Does it run against stable or dev?

Maybe my problems come from this patching error, but I can't make the selector work and I am still watching the header within the splash. Any help? Maybe first correcting the error would be a good line.

Ok, I have tried against dev and patch is failing again when patching js/splashify_init_min.js.rej maybe u can have a look at it

Hehe, correction. The selector works well, I had installed an older stable version. It works perfectly with 7.2. But still there is an error when patching, I had to manually apply js/splashify_init_min.js

Farreres: You can already do this in the config. What this patch does is allows you to use a node for the page instead of entering the html.

Yes, I understand I could add a html code. But in my case, I am displaying as splash a node with panels (or display suite, not sure) but it has a complex content, impossible to use plain html.

I would vote for including this patch into the module, it works nicely!

I would also like to use this feature
Can try the patch but does not look like normal patch file format so I guess it has to be done manually?
+1

In case it helps someone else for now I have decided to use a special page template (e.g. page--node--454.tpl.php) for the node that I am using as the splash page, this allows me to hide the regions I don't want.

gsquirrel: That is a great solution! That is probably the best option for the 7.x branch.

@chrisroane, Thanks.
I followed #3 in order to display an image. Here is an example to save time for someone.

/**
 * Implements hook_menu().
 */
function timehoop_splashify_menu() {
  $items['splashify'] = array(
    'title' => 'Welcome',
    'description' => 'Timehoop',
    'page callback' => 'drupal_get_form',
    'page arguments' => array('timehoop_splashify_display'),
    'access callback' => TRUE,
    'type' => MENU_CALLBACK,
  );
  
  return $items;
}

function timehoop_splashify_display($form, &$form_state) {  
  $form['out'] = array(
    '#type' => 'fieldset',
    '#attributes' => array('class' => array('tp-c-splashify')),
    '#collapsible' => FALSE,
    '#prefix' => '<div id="tp-i-splashify">',
    '#suffix' => '</div>',
  );

  $form['out']['image'] = array(
    '#theme' => 'image',
    '#path' => 'themes/bartik/screenshot.png',
    '#alt' => 'Alternative text',
    '#title' => 'Title',
    '#width' => '400px',
    '#height' => '400px',
    '#attributes' => array('class' => array('tp-c-splashify-tb'), 'id' => 'tp-i-splashify-img'),
  );

  return $form;
}

Does this patch work with 7.x-1.3? I can't get the opacity to change or the colorbox window to just show the content.

I tried locally and on a pantheon server with the same outcome.

Drupal 7.31
PHP 5.3

The patch has been added to 7.x-1.3 and I tried it twice. I can see the opacity and page selector fields but the opacity is not changing. And the header/footer is still displaying in the window.

I add the patch to 7.x-1.3 just on my computer:)

Boriana,

Thank you so much. The splashify_init_min.js file didn't get patched so I made the change manually and the patch works as advertised!

Thanks, John

Excellent work on this essential feature.

Patching worked on the 1.3 release (except the minified js, which required manual copy/paste).

One note: Make sure to activate the option "Enable Colorbox inline" within the Colorbox "EXTRA FEATURES" setting. I was missing this and reckoned the patch wasn't working.

Now happy. Thanks Boriana!

Thank you, Boriana, your patch in #8 works fabulously and is exactly what I needed!

I did have problems patching the min.js, so used the js compress link you gave.

@visios, thanks for the note about Enabling the Colorbox inline - I would also have though it not to be working.

+1 for adding this to the 7x module

After re-reading this thread, and seeing the 12 followers, I've changed my mind. I think this is a needed feature.

ditcheva: I think the way you did this is useful, but I think in most cases people will probably want to load a node directly. So instead of grabbing the contents of a div, I created a node ajax page that looks like this ( _splashify_ajax/[nid] ), which has the sole purpose of outputting the html of the full view mode of a node. If that nodes is used on the What tab, we use that url outside of an iframe. This can be used to output a webform or any other kind of node.

Here is a screenshot in what it looks like:

If you want to customize the full view mode, click on the Manage Display tab on the node edit screen (you may need to enable the full view mode). We like to use Display Suite to give us additional control.

I pushed this to the dev branch. If I can get help in testing this code, I can probably get this pushed in a new version in the next week or so. Let me know if this solves the problem you were hoping for.

ditcheva: Displaying the full page view mode would allow you to customize the output, including not displaying the title, etc.... I can't remember if this is in default drupal, but I know display suite provides a lot of functionality on the view mode screen for customizing each view mode.

I'm open to other ways of doing this, but I think the node approach might be the simplest way to handle it for non technical users. Let me know if anyone has any other ideas in how to handle. Thanks!

The patch is awesome. Tested with webform to load in splashify

Mind-breaking task : )

To display content only i've just created "page--splashify-splash.tpl.php" with:
<?php print render($page['content']); ?>

Hey guys,

How does this work? I've just installed the latest dev version but I don't see any extra settings to the effect of hiding theme regions when the splash page displays in a colorbox overlay.

I'm also still getting all the theme regions, no matter what I set as the "what" option.

Thanks in advance

As I stated earlier..
You should create a ...tpl.php right inside the module's folder.
This way the module will start displaying page content only, without other theme stuff.

@i3laze: but the name of the .tpl.php should match the name of the url in Paths or Url Values? Is the page-- prefix needed?

In my case I have an url named desktop-splash-page which comes from a display suite or panels page. What should I put as file name?

Did this make it to the Drupal 8 version?
I just see a dropdown field that say "plain text" or "use template" but no explanation as to what that means.

Hi all,

I tackled this by taking a slightly different approach to setting up Splashify (awesome module btw, thank you so much!).

I'm using a custom content type for splash pages and created a barebone tpl for it in my theme. I then use the URL options and colorbox rendering in the Splashify config.

I'd recommend using something like the context module, perhaps combined with the context_respect module to prevent any stubborn blocks from ending up on your splash page, should that be the case.

Also, this makes the module compatible with multi-lingual websites, as is requested here: https://www.drupal.org/node/2417135

The cool thing about this approach is that you can include custom regions inside your splash node tpl and use views (or other means) to, for instance, render advanced_link fields as buttons and place them inside layouts you've coded or are provided by panels/ display suite.

Using this approach opens up a whole new box of opportunities :)

The only thing that would be nice to have is to be able to define a splash node per URL, instead of the two options available now, a random url from a list, or the next url from a list. That would put a cherry on the top :)

Hope this is of some help to some of those struggling with this.

Since I'm at it, I'd like to share another another tip that was of great use to me, I use the latest dev version because it allows to set a delay and auto-close through the admin interface.

Also, I'm setting a percentage for the colorbox width and height (50%x50%). That way I don't even require mobile detect.

Have fun!

Did anyone ever figure this out? (It seems so.)

I've patched the module and created .tpl files named page--splashify-splash.tpl.php as specified in both the theme and module folder and I'm still getting the full page content no matter what I do.

Also, it doesn't look like I can hide the regions in colorbox using CSS, so I'm stuck. Any ideas? Thanks!

Oh - I'm using a Bootstrap subtheme, if that's relevant. (.tpl files need to go in system/templates to mirror the base Bootstrap installation.)

I've still not been able to get the display of a specific part of the page to work and I'm at the limit of what I can do with CSS.

Is there any way that someone could post a working version of the patched module? That would be a huge help... thanks in advance!

D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.