FAQs About The FontStylr Stacks.

We listed below some helpful answers to questions about the FontStylr stacks and using them with the Stacks page plugin and Rapidweaver..

1 - What browsers do the FontStylr stacks support?
Safari, Firefox, Chrome, IE6, IE7, IE8, and IE9. All display and function correctly in each of these browsers.

2 - Can I have more than 1 FontStylr stack on a page?
Yes! Just make sure each FontStylr stack has it’s own unique div name.

3 - Is there a maximum number of FontStylr stacks I can have on a page?
Short answer is no, however most web pages will only need to have 2-5 headlines on them. This is the optimum amount to use and the FontStylr stack font styles will appear almost instantly when displayed in a browser window. We have used as many as 28 headline stacks on a page (see FontStylr Vol. 1 examples page) without any issues to note, although you may encounter a small display delay with that many FontStylr stack headlines displaying, depending on each headline’s font size and overall content length.

4 - Any known conflicts with other Stacks?
Due to the large volume of third party stacks out now it’s impossible to test the FontStylr stacks out with all of them. Our testing along with our beta testers on a variety of third party stacks did not result in any known issues or conflicts.
Please be aware though that possible conflicts could arise on your page when multiple instances of javascripts are used in various third-party stacks on a single Stacks page, so use them with caution as display issues can and may occur on your Stacks page.

5 - Are the font styles used with this Stack licensed for public use?
Yes. All the fonts used in the FontStylr stacks are public fonts. We researched each font style’s license extensively to make sure there were no infringements on any of the fonts by including them with the FontStylr stacks. All the fonts use one of the following licenses: Freeware, SIL Open Font, or Public Domain.

6 - Do the font styles used in the FontStylr stacks support special characters?
Yes. Special characters have been included (embedded) into all the font styles. Note though that since these are free or public domain font faces, that the developers of the fonts may or may not have included every international special character within each font face. So while most of the fonts will support special characters, some of them may not and/or will only offer partial support for special characters.

7 - Why do I jump back to the top of my page when I click on a FontStylr stack with the default null link value in place and the cursor hover state is hidden?
We added in the cursor:default; css style code to remove the hover state change when the cursor is moved over a link enabled FontStylr stack to prevent viewers of your site page from thinking the stack is a link, which in turn would help prevent them from clicking on it. The default browser behavior for a null link is to jump to the top of the page it is on. There is nothing we can do to prevent this from happening. The best solution we found was to simply prevent the viewer from thinking the FontStylr stack text was a link.

FAQs About The Dynamic Content Stacks.

Below we have listed some helpful answers to questions about the Dynamic Content stacks and using it with the Stacks page plugin and Rapidweaver.

1 - What browsers do the Dynamic Content Stacks work with?
All the browsers we used to test these stacks with displayed correctly without any issues. The Dynamic Content stacks work with the following browsers: Safari 3 and 4, Firefox 3.5, IE6, IE7, IE8, and IE9.

2 - Can I have more than 1 Dynamic Content stack page in my site?
Yes, you can have as many Dynamic Content or Dynamic Text stack pages as you want in your Rapidweaver site but each page’s Dynamic Content or Dynamic Text stack’s div name, image file names, and XML text file name must be unique! As long as the file and div names are not the same, your individual Dynamic Content and Dynamic Text stack pages will display correctly.

3 - Will my files be overwritten when I republish my Rapidweaver site files?
No! That’s the beauty of this stack. Since the Dynamic Content and Dynamic Text stacks read in external files to dynamically populate the div in the Dynamic Content stacks area, nothing can be overwritten when any Rapidweaver site files are republished.

4 - What version of Rapidweaver does the Dynamic Content Stack work with?
Any version of Rapidweaver that the latest version of the Stacks plugin works with, will work correctly with the Dynamic Content stack.

5 - My images and copy content are not appearing in my Dynamic Content Stacks area on my Stacks page?
This could be caused by several things. First, make sure you have your XML text file uploaded to your server directory and your images are uploaded to the dcs-images folder on your server directory. Second, make sure your XML file url in the Dynamic Content stacks user interface (HUD) options is correct and is using the full absolute url path (see section 6 and 7 for more details). An example of an absolute url would be this: http://yourdomainname.com/DCS-Default.xml.
*Note that some servers configuration may require you to add in the www. prefix too and use
http://www.yourdomainname.com/DCS-Default.xml instead, but most will not.

Last, make sure the individual image urls you have in your XML text file are correct and are the full absolute paths to your image files in the dcs-images folder.