Kieran's dashboard

With the new installer we released on Saturday, Sept. 13, this issue is resolved. Flypaper should install just fine with .net 3.5 and SP 1.
Thanks

Our thoughts for the soundtrack audio is that it would serve as narration or background music, and we do not yet have the ability to stop and start that audio from a button on a page. In the current version of Flypaper, you can put the audio files on the page and use the show/hide features of the buttons to "hide" the audio when the video "shows" and vice versa.

Thanks

Rachel's right. The reason it happened so fast is hackers were trying to attack us through the old forum. We had to move quickly to stop the attack, which was causing delays on the server. We will try to do our best to repost the old forums ASAP. The old forums will be "read only" and all the new posts will be done here on getSatisfaction.com.

Thanks – Kieran, on September 14, 2008 16:31

On Saturday, Sept. 13 we released version 1.02. Stories that were created before July 22, 2008 (in Beta II of the software), shared on flypaper.net and then embedded on a different website with the auto-start property set to false, suddenly started on their own after our new version was released:

The fixes:
Option 1: Open the story in Version 1.02 and share to flypaper.net again with the Flyplayer set to on. Open the story (either from the blue link at the end of the share process -- or on your uploads section of your account page). Click embed in the FlyPlayer and copy the new embed tag to your own website.

Option 2: Edit your embed tag to include the auto-start=false tag. Like:
Change the item_id to the ID of your story (which appears in other sections of the embed tag.

More Details -- The Cause:

In Beta II of Flypaper we had a property inside the Flypaper application to turn auto-start on or off. We removed that feature in Version 1.0 and moved the auto-start property to the embed tag instead. Why? Sometimes people want a story to autoplay and sometimes they want it to be like a YouTube video and not autoplay. They make that decision when they embed the story, so rather than have the Story have one preset behavior, we moved the choice to the embed tag.

In the 1.02 release we stopped supporting the Beta II embed tags.

If you need help with the embed tags, please go to www.flypaper.com/support, and send us an e-mail. We'll help you get the version you need.

This issue was reported and solved by one of our users Christoph...

I've come across an inconvenience which causes Flypaper to display a wrong time in the time-in/time-out dialogs - this is due to my regional settings which are set to a profile that uses a "," as decimal symbol (instead of the more common ".").

How to Fix:

In Control Panel->Regional and Language Options set the region to "English (United States)" (probably any profile with "." as a decimal symbol will work, but I haven't verified that);

Although different regional settings screw up the display, they do not change the actual stored value: even though the "time in" changes from 1 to 100 seconds, the component will still appear after 1 second.

Changing the regional settings to "English (United States)" makes the problem disappear.

Cheers,

-Christoph

We are working on a better solution, but the current workaround is to restart Windows. This seems to clear all the settings and work for every browser. We apologize for the inconvenience.

Flypaper uses the Huffy 2.1.1.1 codec to render video. It is included in the Flypaper installer. Sometimes that installer does not register correctly with Windows or a different version of the codec may be installed on your computer. Other programs use this codec as well.

When there is a problem, you will see a variety of different errors when trying to save a Flypaper Story as a video. Get the zip file with the Huffy files.

1) Download the zip file
2) Extract it to a folder on your computer
3) Right-click the Huffy.inf file and select Install

The codec should install in just a few seconds. Restart Flypaper and Save as video.Download the zip file
2) Extract it to a folder on your computer
3) Right-click the Huffy.inf file and select Install

The codec should install in just a few seconds. Restart Flypaper and Save as video.

Flypaper requires Microsoft's .NET 3.5 be installed before Flypaper can be installed.

Occasional Microsoft .NET 3.5 installation failures are a known issue in the .NET development community. Evidence suggests that various software configurations can cause the installation/upgrade of .NET 3.5 to fail.
We are working hard to better understand this issue. But because it’s related to .NET 3.5 and your operating system (versus Flypaper and your operating system), we have only so much control over the solution.

We have two suggestions to help you correct any issues with .NET 3.5 installation:

Suggestion 1:
Upgrade to .NET 3.5 directly from Microsoft’s site.
We’ve had some success when users upgrade directly from Microsoft’s Web site.
To upgrade directly from the Microsoft site:
1. Restart your computer to clear the current .Net 3.5 installer issue.
2. Go directly to the Microsoft .NET 3.5 installer page located at Microsoft:

3. Read the text, and then click the Install button.
4. Once installation is complete, restart the computer.
5. Install Flypaper.

Suggestion 2:
Completely uninstall .NET from your PC, and then install .NET 3.5 directly from Microsoft’s site.
In some instances, it may be better to completely uninstall .NET first then reinstall as above. But before you do so, please read the following advisories:
ADVISORIES:
• Given that .NET may not be properly installed on your computer, the uninstall/reinstall process may cause other problems on your PC. Uninstall/reinstall at your own risk.
• Other applications that require your current version of .NET may stop running. Again, uninstall/reinstall at your own risk.
• Depending upon your Internet connection speed, this process may take considerable time.
To upgrade directly from Microsoft:
1. Restart your computer to clear the current .Net 3.5 installer issue.
2. Go to your Control Panel and uninstall the current Microsoft .NET Framework.
NOTE: You may be prompted to reboot to complete the uninstall process. When you log back to your PC, Windows Update should might prompt you to install the .NET an update. Please follow the prompts to do so. If Windows Update fails to prompt you to install the .NET update, go to Step 3. This windows update will only install .NET 2.0 and then require you to restart your computer before you can install .NET 3.5. If you continue to the .NET 3.5 installer without doing the update .NET 2.0 will be installed as part of the .NET 3.5 installation.
3. Open a browser and go to the Microsoft .NET 3.5 installer page located at Microsoft

4. Read the text, and then click the Install button.
5. Once installation is complete, restart the computer.
6. Install Flypaper.

For an easier to read PDF document with these same suggestions, click here.

Microsoft just released Service Pack 1 for .NET 3.5. Flypaper requires .NET 3.5 for a number of features --especially for improving the connection from the desktop application to the web-based community. In most cases Flypaper works well with Microsoft .NET 3.5 Service Pack 1 -- except one.

If you install Microsoft .NET 3.5 and Service Pack 1 before installing Flypaper, the Flypaper installer will prompt: "You need to update to Microsoft .NET 3.5..." The solution is to uninstall .NET SP1 (in some cases you may have to re-install .NET 3.5). The links on Flypaper.com point to the correct install of .NET 3.5, or you can get it here..

At the end of the .NET install you are prompted to get all updates from Microsoft, make sure not to accept the Service Pack 1 update for .NET 3.5 before you install Flypaper. Once Flypaper is installed and operating correctly, you can update to Service Pack 1.

We are working on the issue and will have a new installer that works well with Service Pack 1 available soon.

A few users have reported getting the following error: "Error 1155 instmsi30.exe not found". Looking through Microsoft blogs this can be one of two issues. Your version of the Windows installer needs to be upgraded:

Or:

The .NET 3.5 installation is not complete. The best solution for that is to re-run the .NET 3.5 installer (make sure you do not have the .net 3.5 beta installed).