Custom View UI parts - inconsistent access rights from full UI

I created an elaborate tree folder structure using the SystemAdmin account for a tenant and filled it with images. A tenant Admin account is then used to maintain the images/folders. In the full UI, the tenant admin can move images between folders without problem. An asterisk appears next to the base level folders, but not sub-folders.

When using an embedded custom UI part, and the tenant admin API key, the Move function does not allow for moving images between sub-folders. The expected behavior is that functionality should be consistent with that of the full UI.

Is this a glitch, or a misunderstanding on my behalf?

To clarify, I have also created a brand new group for the tenant administrator, and specifically gave that group Full Access permissions to the gallery, with “Allow subfolders to inherit permissions” ticked… That also didn’t work.

Any help would be much appreciated!

Thanks!

Razuna 1.8.2, Windows Server 2012, MySQL

Hi Catinahat ,

I think the embedded custom UI part maybe the cause affected to the moving images between subfolders from your site.

Could you please help to take a screenshot for us to see how ?

Thanks

Hi Huy,

Thanks for the quick response. I think the direct link would be better to understand what’s going on.

[Link removed for security]

If you try to move any of these images to another folder, you will see that it lists the “EveryPage Gallery” as an option, with a sub-folder arrow beside it. That arrow is however inactive, even though there is clearly another 100+ sub folders under it.

http://imgur.com/a/7s21B

Even stranger, if you try to move the same image a second time, no options for destination folders appear.

At the same time, the same account as the API key can log in to the full interface and move any of the images anywhere they like.

Again, thanks for any ideas you have!

Hi Catinahat ,

Please check our wiki from this link for your reference : http://wiki.razuna.com/display/ecp/How+to+show+dedicated+Razuna+UI+parts+in+your+application

Hope this helps.

Thanks

Hi Huy,
I am very familiar with that page, so unfortunately it does not help.

Is there somewhere I can file this as a bug?

To be clear, the bug is that when using Razuna UI parts in an iframe, the Move functionality does not allow access to sub-folders at any time. The button to expand the folder tree is always inactive.

Thanks

Hi Catinahat ,

You can check Catalina.out log file in Tomcat your Razuna
installation folder , example of this : C:\razuna_tomcat_1_8\tomcat\logs

Hope this helps.

Nothing unusual there… All calls end in a 200.

I think I have found something interesting though. Looking at the console in Chrome, as soon as the “Move file” window is displayed, the error

jquery.tree.min.js:1 Uncaught TypeError: $(…).live is not a function

comes up. So it points to a javascript error within the page logic. This is on a page where I am not actually embedding the UI part, this is just the UI part on its own, the way it would be embedded in an iframe - so it’s not like my page’s javascript is interfering with Razuna’s.

I obviously have no control over the javascript on the page, so I doubt it is something I am doing wrong.

Any ideas?

I have just signed up for a 30 day trial on Razuna.com so that I can show you this bug without the possibility that our setup is somehow at fault.

Please try to move any image from one folder to another sub folder.

https://everypage.razuna.com/index.cfm?fa=c.view_custom&api_key=E5FCD4280616463B81FC673CA4BBDEBF&folderid=FA0258A8035B4BADA670444145B84016&showpart=folder&access=x

It will not happen. The UI part simply does not include the necessary code to support it.

Obviously, embedding any UI part with iframe has its limits. Cross-domain
security, javascript not working across domains, etc. Since your are
running Razuna locally you can work around these issues on your server.

That said, we will not support this functionality in the future as you can
use the API to rebuild just about every aspect in Razuna.

Well, we’re not really talking about any cross-domain security or related limitations. That’s not what’s going on here at all… We expect the Razuna UI part to be completely self-contained, with no scripted access to its parent window - it’s merely displayed in an iframe.

Not that it matters really, because if you’re not supporting this functionality in future releases, there is little point in fixing them now.

My point exactly. Razuna is open source, so you can actually look at the
source and change it to make it work for you…