moodleou / moodle-mod_forumng

ForumNG forum module for Moodle
19 stars 20 forks source link

Unable to add image / attachment when replying to post #42

Open mfindlayated opened 9 years ago

mfindlayated commented 9 years ago

Hi,

We are seeing an issue in Moodle 2.6.2 with v2014073000 of the ForumNG plugin. If you create a new post, and add an image to it, you can do so without error. However, if you try to add an image when replying to a post, you can upload a new image / attachment, but you cannot add files from your recent files or any repositories you may have connected as the icons are not visible from the upload screen. I have attached a screenshot to show the behaviour.

Thanks in advance, Mark. screen shot 2014-12-15 at 14 42 11

mfindlayated commented 9 years ago

Oh, apologies, user also reports that you cannot add image even from upload as you can't finish the upload process, screenshot attached... forumng image upload problem png 1

jason-platts commented 9 years ago

Have you checked your theme?

The standard File picker layout has the action links/tabs on the left rather than above, so this might be an issue in other places.

I'm not so sure that it is forumng specific as in the second grab you can see the forum post buttons, so if the File picker were getting chopped off at the bottom of the reply post iframe you wouldn't see those. Or if it is only on forumng then it is because of the iframe (which the first grab looks like) - there isn't really anything that can be done about that, the File picker seems much larger in your theme than the available space...

mfindlayated commented 9 years ago

Hi, have checked on the 'standard' theme, and also see the issue using that theme. This is only an issue for us in ForumNG, file picker appears as expected in all other tools.

mfindlayated commented 9 years ago

This issue appears to be related to the width settings of the 'reply' page, rather than a file picker issue...

If I go to line 356 of styles.css and comment out the width setting: /max-width:800px;/

this solves the issue in our custom theme, the 'standard' theme, and the 'clean' theme.