JMFilePicker : LISE Content Field Suddenly 200,000px High

[Squire4Hire]

This seems to have happened overnight. I'm baffled by it, but suddenly the JMFilePicker expands to over 200k pixels in height when an image is selected from the dropdown list.

Has anyone encountered this? I've tried uninstalling and reinstalling JMFilePicker and creating a new Field Definition to no avail. It wasn't doing this yesterday, so I can't imagine what happened to cause it.

I've attached an image for reference.

[Squire4Hire]

I've narrowed it down to a JMFP_thumbnail_wrapper class that is inserting a height value for the element inline. Not sure where it's getting the value yet... but I might be able to override with a modification to the JMFP.css file. It should be set to 100% - not as a calculated value... wherever it's calculated.

I'd chalk this up as a bug.

[Squire4Hire]

[removed]

Is there any reason why the height is calculated and not set to 100%?

[Squire4Hire]

Really?? You guys are going to censor me and a suggested fix to an obvious problem in one of the modules?

[Jo Morg]

It's not censorship (please again, read the forum rules)... We just don't allow it here on the forum. You can, however, submit it as a bug report on the Forge, where not only it is allowed, as it is appreciated.
Thank you.

[Squire4Hire]

I tried that Jo, but apparently that's broken too. I'm unable to register as a user to be able to post bug reports - otherwise I would have. I tried registering but I never received a confirmation email with a link to activate. And the system doesn't recognize my email address as valid to resend an email... caught in limbo.

More to the point though - you're suggesting a person must wait months before being able to rectify an issue with a module instead of opening a discussion about the issue on a forum that is intended to help people with problems?

I mean, I get the whole "We can't guarantee the product after the fact" disclaimer... but isn't that kind of the point of open source software?

Just out of curiosity - when are you planning on releasing an update to JMFilePicker? It's going on 6 months since initial release with significant bugs. If a user were to find solutions to your bugs (such as the one I posted), wouldn't it be in the interest of users to know how to fix it in the interim?

[Jo Morg]

I tried that Jo, but apparently that's broken too. I'm unable to register as a user to be able to post bug reports - otherwise I would have. I tried registering but I never received a confirmation email with a link to activate. And the system doesn't recognize my email address as valid to resend an email... caught in limbo.

Check the spam folder... there have been some problems with our email addresses (as it is typical with forum and other emails with high volume of traffic) that we have been fixing time and time again.

More to the point though - you're suggesting a person must wait months before being able to rectify an issue with a module instead of opening a discussion about the issue on a forum that is intended to help people with problems?

I mean, I get the whole "We can't guarantee the product after the fact" disclaimer... but isn't that kind of the point of open source software?

Well that's not an easy subject... It's a "poor man" quality control: I (and other developers, the CMSMS Dev team included) refuse to give support to hacks posted on the forum. There is little to no control on the quality of the posted solutions, and we are not required to answer all posts (heck there are developers that don't even have an account on the forum). And that may mean that users that have used a certain hack may feel entitled to support from the original developer(s), which is not true nor even realistic. If the suggested fix is posted on the forge, the developers are notified and can test and endorse or not the fix. There is a world of difference...

Just out of curiosity - when are you planning on releasing an update to JMFilePicker? It's going on 6 months since initial release with significant bugs. If a user were to find solutions to your bugs (such as the one I posted), wouldn't it be in the interest of users to know how to fix it in the interim?

I don't have a planned schedule atm... And (according to my previous answer) if the proposed fix is not the correct fix and/or creates more problems than the ones it solves?
No matter how frustrating this may seem to you, trust me, it's always more frustrating to us when we are called to fix bugs not caused by our own code...

[Squire4Hire]

Nothing in my Spam folder - that was one of the first places I looked.

I really don't know what to say. I mean, I really want to say a lot... but I know you don't want to hear it - which makes this even more frustrating.

With no foreseeable release schedule for updates and bugs, what alternative do people have other than to hack your code?

Are suggested fixes allowed in the Forge? Or does a person only post what the problem is in the hopes that someday a developer will track it down and determine where the issue is?

[Jo Morg]

Are suggested fixes allowed in the Forge?

If the suggested fix is posted on the forge, the developers are notified and can test and endorse or not the fix.

As I said, yes.

[Squire4Hire]

So what do I have to do to get that activation email resent?

[Jo Morg]

Honestly, I don't know, maybe someone else from the Dev Team can answer that, however I just tried to create a new account and it worked flawlessly, except for the activation email which was in the spam folder. No biggie though.