Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

I'm getting an error when trying to use SCSetContainer. The error returned states "Missing version header in SuperContainer response" and then advises me to make sure SC is running or update to the latest version. Both SC and the plugin are the latest version (2.852), and SC is running. SCSetContainer is the only function that is causing the problem. I can upload photos using the web viewer, I can get info using SCGetInfo, and I can even go the other direction and put an image into a container field using SCGetContainer, so I'm sure the base URL is set and I have the correct syntax. Any ideas on what could be going on here?

I'm using FMP Advanced 11.04 on Mac OS 10.7.2, with FM Server and SC running on Windows Server 2008.

Hey there,

are you sure that you have updated both the SuperContainer server and the SuperContainer companion plug-in to the latest version (2.852)? What is returned when you enter:

SCVersion

and evaluate it? How are you calling SCSetContainer()? Or, when using a browser and navigating to:

"http://ipOfWindows08server/SuperContainer"

do you receive an html page that displays the current version of SuperContainer you are running? Let me know the answers to these questions so that we can resolve this issue.

Looking forward to hearing from you,

  • Author

I can no longer reproduce this error on either of the two servers it has happening on before. I have had to shut down my client machine (Mac 10.7.2) since then - the only machine I used to produce the error in the first place - so perhaps there was something amiss with the Safari engine that a reboot cleared up. In any case, the problem is gone...

Dave

Sounds good Dave,

I am glad to hear you resolved the issue. Thanks for letting us know what you did to fix the problem.

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.