Same here. All (!) my apps display heights have been reset to 20. If I put them back to their original heights they are reset to 20 as soon I press the Save button. This applies to the profile and home surface (canvas height is still OK).

Major bug.....

Yep, definitely a major bug...

I'd work around it by resizing the height with the adjustHeight() feature, but there's yet another bug that's causing my code edits to not take affect (it's said "Your changes have been submitted for approval." for two weeks now, and the "Publish Changes" button no longer appears. Supposedly, changes I make to the code are still meant to be taking affect, but they're not).

Let me look into this.

Rhonda

Thanks for reporting this bug. It turns out that we're saving the correct value, but the UI always displays "20" in the height field.

Try entering the intended value and ignoring what it says in the box and let me know if that works out. We'll be fixing the issue shortly as well.

 Our app is still experiencing the same problem. We change the height from 20 but it doesn't have an effect on the profile height.

http://profile.myspace.com/index.cfm?fuseaction=user.viewprofile&friendid=360100453 

Our app's display height is set to 20, though I change it.

APP ID: 103685

Please help me.

 Once you render your app - use gadgets.window.adjustHeight(DESIRED_HEIGHT);

 Replace DESIRED_HEIGHT with a number...

even if i wanted to implement a workaround, i couldn't. Im still getting this for an app in dev:

Panel update failed; Update Result: MountPointHasExistingPanel; AppId: 105420; PanelType: OpenSocial

Umang:

 Once you render your app - use gadgets.window.adjustHeight(DESIRED_HEIGHT);

 Replace DESIRED_HEIGHT with a number...

and if you have 350 apps say.. you get to update the source and click save 1050 times (once per surface).

Thus.. having the "source code" be forced to live on anyopensocial provider proves to be rather painful when the opensocial container develops bugs such as these.. on average what.. 3-4 times a week for the last 75 days?

The Apps don't break unless you save them with the height set to 20 -- then, the App's height will be 20.

Which means, yes, if you update the code on a surface, you also have to remember to change the '20' to the proper height before you save. If you've already saved with the height set to '20', you can go back and enter the right height and save it again. The box will still show a '20', but the App will save the height you entered.

There is no need to add gadgets.window.adjustHeight() to each of your Applications.

I'm not making light of the bug -- it's definitely a bug, and it definitely needs to be fixed, but there's no need to go through a lengthy process -- the bug will only affect Apps that get saved without setting the proper Height.

Yeah, this is a pain. I use a single xml for all my surfaces because this is the most cross-platform way I've found. So I have to upload the xml then copy and paste it into the profile and canvas, chaging the height every time. Then when it's all done, I have to remember to reupload the icon and decription, which are deleted when uploading xml.

TK's Apps:

Yeah, this is a pain. I use a single xml for all my surfaces because this is the most cross-platform way I've found. So I have to upload the xml then copy and paste it into the profile and canvas, chaging the height every time. Then when it's all done, I have to remember to reupload the icon and decription, which are deleted when uploading xml.

Plus there is the other problem..if you use an XML URL for an app.. you then can't go back to the canvas/home/profile tabs and change the source and click save (it won't work).

Once an XML app, always an XML app.

excuse my noobishness, but i havn't ever used XML.

is this an alternative to updating source code rather than using "MyApps" - i mean an alternative thats not currently broken?

Not right now -- what they're talking about is the fact that under My Apps, you can specify the URL of a Gadget XML file instead of entering source-code into the editor. Obviously, it's still got some errors, though that is entirely off the topic of what this particular thread is about.