david_wp
Forum Replies Created
-
The behavior is by design. The Access Control ONLY controls access to the Silverlight .xap file source URL. It does NOT manage access for the containing page or post.
If you would like to control access to the page/post as well, I would recommend Justin Tadlock’s Members plugin.
This plugin will control access to the page/post for any user or role and even allows creating custom roles.
A simple example. After activating the Members plugin, each post/page will have a Content Permission box at the bottom. If you would like to restrict ALL content on that page/post to Administrators only, simply check the Administrator box and update the page. Any non-Administrator attempting access will see a message (customizable) that the content is restricted.
Used together with my Simply Silverlight plugin a complete access control solution to pages/posts with Silverlight content is possible.
Thanks again for your interest and use of Simply Silverlight.
I’ve researched the problem and believe I have a solution for you. Edit the file simply-silverlight.php in the plugin’s folder. Look for these lines:
header("Content-Disposition: attachment; filename=\"$requested_xap\""); readfile($filename);
Right below the
readfile($filename);
add this lineob_end_flush();
Save changes and try again. This should work. If it does, please let me know so I can update the plugin in the WordPress repository.
Thank you for your patience.
Yes, use the absolute path on your host. The warning error is gone, so we know the path is valid. Make sure xap file is in your secure path. Verify secure=true attribute is on in code (e.g. [simply-silverlight xap=Mysilverlightfile.xap secure=true]. Login to your site and browse to the post/page with the Silverlight app. If it doesn’t display, then open the page’s source and grab the value for the Silverlight source like in your prior post (e.g. https://www.mywebsite.com/index.php?simply-silverlight=Mysilverlightfile.xap”). Attempt to browse to this path. If the xap can’t be found, you will receive an error message. If it can your browser should download it. Let me know what happens.
First, thanks for using the plugin! Now to your question.
The Secure Path field only accepts local filesystem paths, NOT web URLs. So a path like https://www.mywebsite.com/wp-content/plugins/simply-silverlight/secure/ will NEVER work. What you have to use is a local path, something more like c:\mywebsitepath\wp-content\plugins\simply-silverlight\secure\ if on a Windows host, or /mywebsitepath/wp-content/plugins/simply-silverlight/secure/ if on a Unix/Linux host.
If your site is on shared hosting and you’re not sure what path to use, the plugin can help you out. You’ll need to reset all settings by clicking the Restore Defaults button at the bottom of the plugin settings page. This will, of course, reset ALL the global settings you may have changed including the Secure Path. I’d give this a try. Or…
I’ve just uploaded a new version of Simply Silverlight, 1.0.2. In this version I made it possible to reset the default Secure Path WITHOUT having to reset all settings, in addition to a bug fix. In this version all you need to do is enter “default” into the Secure Path field and save changes.
Let me know if you have any other issues.
-David
Hi jbtroost, thank you for using the plugin. I checked out the site you gave and saved a .xap myself. You are doing everything right. Simply Silverlight IS loading the .xap BUT something’s not right about the file the website creator is producing. I tried to load the .xap with straight HTML outside of WordPress altogether. . . didn’t work. I also used that site’s creator utility to save an HTML version. . . didn’t work either. Only the images saved correctly locally. I would suggest contacting the site owner to report an issue with the utility. But in fairness to the site owner, the function to save .xaps does appear to be in beta so you may want to give them some time. I would be happy to answer any other questions or hear comments. Thank you.
This feature is now available in version 1.0.1 of the plugin. Thanks for using Simply Silverlight.