Moodle Community Sites

Tracker: Problem editing UI mockups

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Component/s: tracker.moodle.org
  • Labels:
    None

Description

I received the following email from Daniel Neis Araujo about editing UI mockups in the tracker and figured I would report it here. Peace - Anthony

— email from Daniel —

Hello,

until yesterday i was able to edit the ui mockups of http://tracker.moodle.org/browse/MDL-17081 but now when i try to open via the balsamiq i got "There was a problem loading the mockup data."
When i try to download the file i get:

System Error

A system error has occurred.

If this problem persists - please notify your JIRA administrator of this problem.

Otherwise, please create a support issue on our support system at http://support.atlassian.com with the following information:

1. a description of your problem
2. cut & paste the error and system information found below

Cause:

Could not find the specified attachment on the server

Referer URL: http://tracker.moodle.org/browse/MDL-17081

Build Information:
Uptime : N/A
Edition : Enterprise
Version : 3.13.5
Build Number : 360
Atlassian Partner : null
Installation Type : EAR/WAR
Server ID : Contact your Administrator to discover this property value.

Server Information:
Application Server: Apache Tomcat/5.5.20
Servlet Version: 2.4

File Paths:
Contact your System Administrator to discover file path information.

Memory Information:
Total Memory: 1156 MB
Free Memory: 788 MB
Used Memory: 368 MB
Total PermGen Memory: 4095 MB
Free PermGen Memory: 4033 MB
Used PermGen Memory: 62 MB

System Information:
System Date : Wednesday, 16 Sep 2009
System Time : 20:30:45 +0800
Current Working Directory : Contact your System Administrator to discover this property value.
Java Version : 1.5.0_11
Java Vendor : BEA Systems, Inc.
JVM Version : 1.0
JVM Vendor : Sun Microsystems Inc.
JVM Implementation Version : R27.3.1-1_CR336511-87524-1.5.0_11-20070817-1359-linux-ia32
Java Runtime : Java(TM) 2 Runtime Environment, Standard Edition
Java VM : BEA JRockit(R)
User Name : root
User Timezone : Australia/Perth
User Locale : English (United States)
System Encoding : UTF-8
Operating System : Linux 2.6.9-67.ELsmp
OS Architecture : i386
Application Server Container :
Database type : mysql
Database JNDI address : java:comp/env/jdbc/JiraDS
Database URL : Hidden
Database version : 4.1.20
Database driver : MySQL-AB JDBC Driver mysql-connector-java-3.1.12 ( $Date: 2005-11-17 15:53:48 +0100 (Thu, 17 Nov 2005) $, $Revision$ )
External user management : OFF
Crowd integration : OFF
JVM Input Arguments : Contact your System Administrator to discover this property value.

Language Info:
Installed languages: Catalan (Spain)
Chinese (China)
Chinese (Taiwan)
Czech (Czech Republic)
Danish (Denmark)
Dutch (Belgium)
English (UK)
English (United States)
French (France)
German (Germany)
German (Switzerland)
Hungarian (Hungary)
Italian (Italy)
Japanese (Japan)
Norwegian (Norway)
Polish (Poland)
Portuguese (Brazil)
Russian (Russia)
Slovak (Slovakia)
Spanish (Spain)
Turkish (Turkey)
Default language: English (United States) - System Default

Request Information:

  • Request URL: http://tracker.moodle.org/500page.jsp
  • Scheme: http
  • Server: tracker.moodle.org
  • Port: 80
  • URI: /500page.jsp
  • Context Path:
  • - Servlet Path: /500page.jsp
  • - Path Info: null
  • - Query String:

Request Attributes

  • javax.servlet.forward.request_uri : /secure/attachment/18381/Pre-import-screen.bmml
  • javax.servlet.forward.context_path :
  • javax.servlet.forward.servlet_path : /secure/attachment
  • javax.servlet.forward.path_info : /500page.jsp
  • javax.servlet.error.message : Could not find the specified attachment on the server
  • com.atlassian.gzipfilter.org.tuckey.web.filters.urlrewrite.RuleMatched : true
  • com.atlassian.gzipfilter.GzipFilter_already_filtered : true
  • gzipMimeTypes : text/.*,application/x-javascript,application/javascript,application/xml,application/xhtml+xml
  • javax.servlet.error.servlet_name : viewattachment
  • atlassian.core.seraph.original.url : /secure/attachment/18381/Pre-import-screen.bmml
  • os_securityfilter_already_filtered : true
  • com.atlassian.jira.web.filters.ActionCleanupDelayFilter : true
  • javax.servlet.error.request_uri : /secure/attachment/18381/Pre-import-screen.bmml
  • javax.servlet.error.status_code : 500
  • com.atlassian.johnson.filters.Johnson503Filter_already_filtered : true
  • com.atlassian.jira.web.filters.RequestCleanupFilter_already_filtered : true
  • jira.webwork.cleanup : false
  • loginfilter.already.filtered : true
  • webwork.result : Value stack =========== ===========
  • com.atlassian.core.filters.HeaderSanitisingFilter_already_filtered : true

Request Logging
0 log statements generated by this request:

Listeners

  • Issue Cache Listener (com.atlassian.jira.event.listeners.cache.IssueCacheListener)
  • Issue Index Listener (com.atlassian.jira.event.listeners.search.IssueIndexListener)
  • Mail Listener (com.atlassian.jira.event.listeners.mail.MailListener)

Services

  • Backup Service (com.atlassian.jira.service.services.export.ExportService)
  • Delay: 1440 minutes
  • Mail Queue Service (com.atlassian.jira.service.services.mail.MailQueueService)
  • Delay: 1 minutes
  • VCS Update Service (com.atlassian.jira.service.services.vcs.VcsService)
  • Delay: 33 minutes
    Plugins
  • Admin Menu Sections 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • Balsamiq Mockups 1.5.28 - Plugin by Balsamiq Studios, LLC
  • Enabled
  • Browse Project Operations Sections 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • Content Link Resolvers Plugin 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • Custom Field Types & Searchers 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • FishEye Plugin 2.2.2 - Plugin by Atlassian Software Systems
  • Enabled
  • ILOG Security Level Searcher plugin 1.0 - Plugin by ILOG
  • Enabled
  • Issue Operations Plugin 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • Issue Tab Panels Plugin 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • Issue Views Plugin 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • JIRA Bamboo Plugin 2.3.1 - Plugin by Atlassian Software Systems Pty Ltd
  • Enabled
  • JIRA Footer 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • JIRA Toolkit Plugin 0.7.30 - Plugin by Atlassian Pty Ltd
  • Enabled
  • Moodle Branches Custom Fields 1.0.1 - Plugin by Eloy Lafuente (stronk7)
  • Enabled
  • ParentField 0.2 - Plugin by PCI
  • Enabled
  • Portlets Plugin 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • Preset Filters Sections 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • Project Panels Plugin 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • Project Role Actors Plugin 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • RPC JIRA Plugin 3.13.1 - Plugin by Atlassian Software Systems Pty Ltd
  • Enabled
  • Renderer Component Factories Plugin 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • Renderer Plugin 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • Reports Plugin 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • Top Navigation Bar 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • User Format 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • User Navigation Bar Sections 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • User Profile Links 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • View Project Operations Sections 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • Web Resources Plugin 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • Webwork Plugin 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • Wiki Renderer Macros Plugin 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled
  • Workflow Plugin 1.0 - Plugin by Atlassian Pty Ltd
  • Enabled

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Anthony Borrow added a comment -

Jordan - I have added Daniel as a watcher of this issue should you have any questions for him. I wonder if this might be related to the recent tracker upgrade. Thanks for looking into this. Peace - Anthony

Show
Anthony Borrow added a comment - Jordan - I have added Daniel as a watcher of this issue should you have any questions for him. I wonder if this might be related to the recent tracker upgrade. Thanks for looking into this. Peace - Anthony
Hide
Permalink
Jordan Tomkinson added a comment -

This has been fixed, thanks.

Show
Jordan Tomkinson added a comment - This has been fixed, thanks.
Hide
Permalink
Elizabeth added a comment -

Hi everyone,

I have the same problem and I do not know what to do. I am sure that the attachment path is set correctly.

Our company wanted to 'merge' two environemnts (production and develeopment ones).

During the merging process we opened a (new) test JIRA instance, where all the settings came from the production environment. Then we did a full backup from production environment (2 projects and issues related to them, users, groups etc.). After that we created new projects, workflows, permission schemes etc. Everything was all right on this test instance (attachments are still accessible), so we decided to do a full backup on production environment from the test instance. Then this problem appeared. All the files that were attached in production environment before migration are not accessible for a jira user (they exist, since they can be downloaded from the server), however all the files attached after migration are accessible.

Re-indexing, shutting down and starting up JIRA again failed.

Eliza

Show
Elizabeth added a comment - Hi everyone, I have the same problem and I do not know what to do. I am sure that the attachment path is set correctly. Our company wanted to 'merge' two environemnts (production and develeopment ones). During the merging process we opened a (new) test JIRA instance, where all the settings came from the production environment. Then we did a full backup from production environment (2 projects and issues related to them, users, groups etc.). After that we created new projects, workflows, permission schemes etc. Everything was all right on this test instance (attachments are still accessible), so we decided to do a full backup on production environment from the test instance. Then this problem appeared. All the files that were attached in production environment before migration are not accessible for a jira user (they exist, since they can be downloaded from the server), however all the files attached after migration are accessible. Re-indexing, shutting down and starting up JIRA again failed. Eliza
Hide
Permalink
Jordan Tomkinson added a comment -

Elizabeth,

You have to manually copy the Attachments directory of your old jira installation to the new one.
Also please be aware this tracker is for support of Moodle software, not Jira. you should open a ticket at http://support.atlassian.com

Show
Jordan Tomkinson added a comment - Elizabeth, You have to manually copy the Attachments directory of your old jira installation to the new one. Also please be aware this tracker is for support of Moodle software, not Jira. you should open a ticket at http://support.atlassian.com
Hide
Permalink
Elizabeth added a comment -

The attachemnts were copied to the desired directory. There is now problem with the newer ones, although they are in the same directory as the older ones (created before migration).

I know it is not a jira tracker, but I have exactly the same problem.

Show
Elizabeth added a comment - The attachemnts were copied to the desired directory. There is now problem with the newer ones, although they are in the same directory as the older ones (created before migration). I know it is not a jira tracker, but I have exactly the same problem.
Hide
Permalink
Jordan Tomkinson added a comment -

Then it may be a permissions problem, does the Tomcat/Jira user have write permissions on all folders?
Our original issue was fixed with an rsync of the old attachment directory to the new one, with the Update and Keep Existing flags turned on
Have you sought help at the atlassian forums? Have you asked your system administrator to look into this?

Show
Jordan Tomkinson added a comment - Then it may be a permissions problem, does the Tomcat/Jira user have write permissions on all folders? Our original issue was fixed with an rsync of the old attachment directory to the new one, with the Update and Keep Existing flags turned on Have you sought help at the atlassian forums? Have you asked your system administrator to look into this?
Hide
Permalink
Jordan Tomkinson added a comment -

Closing this issue, recent comments are not related to the original issue.

Show
Jordan Tomkinson added a comment - Closing this issue, recent comments are not related to the original issue.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Moodle. Try JIRA - bug tracking software for your team.