Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsIFrameIFrameQuery String fails because of PermissionQuery String fails because of Permission
Previous
 
Next
New Post
11/13/2008 11:30 PM
 

We're using DNN 4.9 with IFrame 4.3

We have a flash app within an IFrame.  The App is embedded and exposed using a html page.   The flash app accepts several 'var' value from the object getPageParameter().   So,we have setup three Query String parameters using the same naming convention to pass static values to the app.  All seems to work according to plan.  Except, the user needs edit permission to view the results.  Whenever the user is in Edit mode, everything work perfectly.  When the user is in View mode  -nothing. 

Is this the entended workflow?

Any suggestions are appreciated.

Cheers,

 

 


Incredible PeopleWare.Canada
 
New Post
11/17/2008 12:49 PM
 

So, you have an HTML page with a Flash app embedded on it. You are including that HTML page inside the IFrame module and pass 3 parameters to that page which are picked up by the IFrame?

So, what do you mean by "Except, the user needs edit permission to view the results. " ? The fact that without Edit rights nothing is visible?  Or are you talking about the View/Edit/Design modes up on top in the Control Panel? 


Vitaly Kozadayev
Principal
Viva Portals, L.L.C.
 
New Post
11/22/2008 3:53 PM
 

Hi Vitaly,

Thanks for the reply,

We are using the HTML page inside the IFrame module and passing three parameters to that page which are picked up from the IFrame. for example "User's First Name"

What is meant by "user needs edit permission to view the results" is.... this is the failing condition.  Example:A User with edit permission  to the page selects Edit mode on the top of the page and the IFrame instance produces the expect results.  The expect results being QueryString parameters are passed to the HTML page's pageObject.  When the user's selected mode is View the Iframe instance is unsuccessful in passing the the QueryString parameter to the the pageObject. 

 

 

Is this the expected work flow?  If not, any suggestions would be appreciated.


Incredible PeopleWare.Canada
 
New Post
11/23/2008 10:06 PM
 

 It shouldn't matter. There is no "built-in" correlation between View/Edit modes and IFrame visibility. There could be some issues with IFrame browser security levels.

I've been fighting some oddities here and there seemingly related to that. Is your html page on the same domain as DNN?


Vitaly Kozadayev
Principal
Viva Portals, L.L.C.
 
New Post
11/25/2008 1:07 AM
 

Hi Vitaly,

Thanks for your reply.  It is appreciated.  This is absolutely a cool tool.  When this workflow functions, it will be even cooler.  The Html is using a sub-domain to the portal domain and running within a seperate application pool.

-D      


Incredible PeopleWare.Canada
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsIFrameIFrameQuery String fails because of PermissionQuery String fails because of Permission


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out