Activity
From 2011-06-14 to 2011-06-16
2011-06-16
-
23:15 Feature #8635 (Closed): Composição dos Grupos
- Composição parcial: Erika, Carmem, Diógenes
-
23:07 Defect #8634 (Closed): Projeto Saude UnB
- Projeto para elaboração de um produto com finalidades educativas sobre as doenças sexualmente transmissíveis.
-
22:47 Defect #8633 (Closed): Pagination counts non visible issues
- When I see my list issues the projects (with various subproject) with filter status: all, in result show me
> > 1 2 3 4 Next » (1-100/398) | Per page: 25, 50, 100
In first page show me 100 issues, the second show me 1 issue, the t... -
22:05 Defect #8089: Error trying to delete XML attachment
- I had the same problem again, but now with a htm file. And same error on the log, about permissions. But then I logged with a different Redmine user, and it worked. How come?
-
19:11 Defect #7688: Redmine's trunk (rails 2.3.11) doesn't work with Mongrel 1.1.x
- Thanks for the clarification. I see a lot of trouble with Debian ruby gems packages...
-
18:49 Defect #7688: Redmine's trunk (rails 2.3.11) doesn't work with Mongrel 1.1.x
- Thanks for your answer Etienne... I found the problem... We did not install mongrel gems. We installed mongrel directly with apt-get.
The first IF in mongrel.rb patch asks for the RAILS version (2.3.11), ok... and for the GEM MONGREL... -
17:20 Defect #7688: Redmine's trunk (rails 2.3.11) doesn't work with Mongrel 1.1.x
- Did you restart your server ?
-
16:31 Defect #7688: Redmine's trunk (rails 2.3.11) doesn't work with Mongrel 1.1.x
- Hi, I placed both files "mongrel.rb":https://gist.github.com/826692 and "patch_for_mongrel.rb":http://www.redmine.org/attachments/4699/patch_for_mongrel.rb in /<my-redmine-path>/config/initializers/ plus "rails_6440_patch.rb":http://www...
-
19:10 Defect #8524 (Closed): Error upgrading from 1.1.1 to 1.2.0
-
18:55 Defect #8524: Error upgrading from 1.1.1 to 1.2.0
- Hi, you have to place the mongrel.rb file in your redmine/config/initializers. We had a problem with the gems. We didn't install mongrel and mongrel_cluster gems. If you look at the patch code, the first IF sentence is searching for the ...
-
19:07 Defect #8623: Wiki Formatting Issue
- This actually does look right in some browsers, but I don't think the generated HTML is correct with regards to the paragraph tags. Here is another problematic structure:
# Adding a table to a numbered bullet
|_. HI|_. BYE|
|0|1|
... -
00:49 Defect #8623 (New): Wiki Formatting Issue
- 1. your database version - MySQL 5.1.56
2. your Ruby version - 1.8.7 (i686-linux)
3. your Rails version - 2.3.11
Take a look at the output of the text below. Lines 1 and 2 should be separated by a newline.
Formatting ... -
18:52 Defect #7857: A NoMethodError occurred in account#login
- Thanks for clarifications. As I commented in http://www.redmine.org/issues/7688, our problem was not having installed the mongrel gems. Once installed, just with mongrel.rb in /config/initializers, everything is working. :)
-
17:18 Defect #7857: A NoMethodError occurred in account#login
- * mongrel.rb is mandatory to get mongrel 1.1.5 work with RoR 2.3.11. It's the only patch I'm actually running with.
* patch_for_mongrel.rb might be useful for a sub-URL Redmine setup ?
* rails_6440_patch.rb might be useful at start to ... -
16:17 Defect #7857: A NoMethodError occurred in account#login
- Hi everybody, we are trying to upgrade to 1.2 and we are having both problems here described... the problem is that after applying what here is detailed... there is no way... problems still remain.
Please, let me know if I'm missing ... -
17:13 Feature #8598 (New): links to email for any user
-
12:31 Feature #8598 (Resolved): links to email for any user
- agkljadl
-
17:12 Feature #8632 (Closed): Фото переводчик
-
15:14 Feature #8632 (Closed): Фото переводчик
-
13:17 Feature #8631 (New): History for users,versions, projects changes
- I am storing in projects(users, versions) custom fields too important information.
I need to story and view journal changes for projects(users,versions). -
13:11 Feature #8630 (New): Journals in REST API
- I need to view journals information in REST API.
Features:
* search by create_on in journal
* search by custom_field or field (issue or may be something else)
* search by user_id
* search by journalized_id, journalized_type
-
11:32 Feature #8597: Missing groups related array in users.xml
- I need this feature too )
-
10:22 Feature #8629 (New): Allow assigning issues and/or watcher status to authenticated non members
- This feature request is vaguely similar to #7342 but that issue doesn't particularly fulfill this request.
Our redmine installation is configured to require authentication for access and for manual account activation for self register... -
09:50 Defect #8628 (Closed): "Related to" reference may yield circular dependency error message
- The "related to" reference is neither directed nor declaring a dependency. Thus the error "This relation would create a circular dependency" seems wrong. "Related to" references should be possible in any case, should they not?
-
09:48 Feature #8627 (New): Issue Atom/RSS feed filters
- It would be massively helpful if the Atom feed on the Issue list included the current filters as parameters, so that the feed could represent a subset of the full issue list.
I think I had a look at this at one point, but was quickly ... -
07:31 Defect #8626 (Confirmed): Setting status via API fails silently
- When a user attempts to set the @status_id@ of an issue, but does not have permission to do so, Redmine's API does not respond with an error. The status is not updated, yet the response still indicates success.
I tested this with Adm... -
07:23 Feature #7506: Include allowed activities list in "project" API response
- I meant #7819, not #7402.
-
07:14 Feature #7506 (Resolved): Include allowed activities list in "project" API response
- This is duplicate of one or some of the following;
* #4968
* #7180
* #7402 -
07:19 Feature #4968: REST API new features
- I meant #7819, not #7402.
-
07:16 Feature #4968 (Reopened): REST API new features
- I am reopening since #296 is done and dusted, but these features did not get in yet.
This is related or duplicate of #7180 and/or #7402.
It would be great to get this or one of those reviewed and committed. -
06:58 Feature #4968: REST API new features
- Yohann; What is the status of your Redmine fork on GitHub? Are you merging Redmine's changes into your fork? Have your changes been contributed back to Redmine? Will they? Are you still contributing to the Redmine project? Thanks f...
-
07:19 Feature #7180: List of statuses in REST API
- I meant #7819, not #7402.
-
07:16 Feature #7180: List of statuses in REST API
- This is related or duplicate of #4968 and/or #7402.
It would be great to get this or one of those reviewed and committed. -
07:19 Feature #7402: REST API - Enumerations
- I meant #7819, not #7402.
-
07:14 Feature #7402: REST API - Enumerations
- This is duplicate of one or some of the following;
* #4968
* #7180
* #7402 -
07:18 Defect #7819: REST API Populating issue field enumerations + Issue list filters
- This is related or duplicate of #7180 and/or #4968.
-
07:08 Defect #7819: REST API Populating issue field enumerations + Issue list filters
- It would be great to get this reviewed and committed.
-
06:56 Feature #7420: Rest API for projects members
- Related; http://www.redmine.org/issues/4968
-
06:54 Feature #7420: Rest API for projects members
- An API to create, read, update and destroy members (user:project relationships with a "role") would be useful.
-
06:51 Defect #8199: Unable to change the status of an issue regardless of workflow
- Related; http://www.redmine.org/issues/8625
-
06:51 Defect #8625: Admin can not change issue status
- Related; http://www.redmine.org/issues/8199
-
06:50 Defect #8625 (Closed): Admin can not change issue status
- Using a default instance of Redmine with no changes to workflow configuration or other global settings, Redmine Administrator users can not change the status of tickets until she is a member of the project.
Is this a feature or a bug? -
05:36 Defect #8612: Custom Field Update gives Internal error
- Yes, the tables character set to UTF - 8.
I tried inserting the values manually and able to succeed. -
01:43 Defect #8291: Issued refed/closed by repository commit message don't show as associated revisions if issue is in a different project to the repository
- Is the repository module enabled on the sub-project? It needs to be, even if it's not used/configured directly.
-
01:26 Defect #8610: Visiting revisions should try to update revisions before issuing a 404
- Etienne Massip wrote:
> Dave Abrahams wrote:
> ...
Done; see #8624 -
01:25 Feature #8624 (New): revisions should always be automatically fetched
- I consider it a usability bug that a project's changes/ and revisions/ URLs behave differently per #8610. People will notice the revisions/ URL in their browsers' address bars and assume—as I did—that it's a legitimate and reliable way ...
-
00:11 Defect #8225: Revisions that reference issues are duplicated if their repository is listed for a project and its subprojects
- The patch is flawed. If the subproject has a repo that is different from the parent project but the commit message in the subproject repo references an issue in the parent project (I do this all the time) then the issue would not be link...
2011-06-15
-
23:30 Defect #8610 (Closed): Visiting revisions should try to update revisions before issuing a 404
- Dave Abrahams wrote:
> 1. is the difference between /revisions and /changes documented somewhere?
Looked for it quickly in wiki but didn't find anything relevant; as I said, I'm not sure to understand the acutal behavior, so I guess ... -
17:28 Defect #8610 (Reopened): Visiting revisions should try to update revisions before issuing a 404
- 0. Thanks for the information; that's a big help!
1. is the difference between /revisions and /changes documented somewhere?
2. Do I really have to open a new ticket to flag this as a design/usability bug?
-
14:01 Defect #8610 (Closed): Visiting revisions should try to update revisions before issuing a 404
- Dave Abrahams wrote:
> I just visited http://mysite.com/projects/xxxx/repository/revisions/a1d98298d2c7bc8d0533b299c418526b8a11d85a and got an immediate 404. Then I visited http://mysite.com/projects/xxxx/repository and there was a lon... -
06:44 Defect #8610: Visiting revisions should try to update revisions before issuing a 404
- ed brown wrote:
> is it a real website? if it is and you know the owner contact them or maybe they deleted it too
Yes, it's a real website but I obfuscated the URL because you can't see the real website anyhow; it's password-protecte... -
04:18 Defect #8610: Visiting revisions should try to update revisions before issuing a 404
- is it a real website? if it is and you know the owner contact them or maybe they deleted it too
-
03:33 Defect #8610 (Closed): Visiting revisions should try to update revisions before issuing a 404
- I just visited http://mysite.com/projects/xxxx/repository/revisions/a1d98298d2c7bc8d0533b299c418526b8a11d85a and got an immediate 404. Then I visited http://mysite.com/projects/xxxx/repository and there was a long delay before anything ...
-
23:20 Defect #8622 (Closed): dasdasd
-
23:05 Defect #8622 (Closed): dasdasd
-
23:19 Feature #8621 (Closed): gsgs
-
19:27 Feature #8621 (Closed): gsgs
- gsdsagagfwa
-
19:56 Feature #6721: Allow setting issue assignment by username via REST interface
- this feature would be VERY useful for my application. I currently have to use "Admin" user to create tasks, which is a bad solution
-
19:17 Defect #8620 (New): The time tacking can't calculate the parent timing in Roadmap page
- After I assign a version with several parent task issues.
The "Estimated time" and "Spent time" are alway 0 in Roadmap page.
It should sum all the parent tasks' timing.
-
18:20 Defect #8619: Git: 404 just for looking at the "repository" tab
- Have a look at @production.log@ ?
-
17:37 Defect #8619 (Closed): Git: 404 just for looking at the "repository" tab
- I have a project using a Git repo. Clicking the repository tab used to work; now I just get a 404. I'd point you there but it's password-protected. How can I debug this?
-
18:19 Feature #8531 (Closed): Task's "assignee" should be specified by login instead of user ID
- Closed as duplicate of #6721, thanks.
-
17:18 Feature #8531: Task's "assignee" should be specified by login instead of user ID
- Duplicate of #6721
-
17:14 Feature #8618 (Closed): New Permission: View Forum
- Most of the Permission do have a View XXXX checkbox, but not the forum. In my case i wanted to give a customer access to our redmine. In fact he is able to see our discussion forum which is not ment to be public. Its definetly a missing ...
-
17:03 Feature #1189: Multiselect custom fields
- +1
-
16:54 Defect #8325: undefined method `name' for "actionmailer":String (RubyGems > 1.6 not supported)
- Nikola Kotur wrote:
> Also got bit by this while upgrading Redmine to 1.2.0.
> ...
This is not a bug, latest stable doesn't work with RubyGems > 1.6 because Rails 2.3.11 doesn't work with RubyGems > 1.6 as stated in [[RedmineInstall#Re... -
15:58 Defect #8325: undefined method `name' for "actionmailer":String (RubyGems > 1.6 not supported)
- With the following gems it works:
Rails (2.3.11)
i18n (0.4.2)
rack (1.1.1)
rake (0.9.2)
rubygems-update (1.6.0) -
16:30 Patch #8617 (Closed): Indent subject of subtask ticket in exported issues PDF
- I opend a List of ticket on the web view, subject of subtasks is indented.
But when I opend exported PDF, subtasks is not indented.
This patch is improvement to exported PDF indent. -
16:13 Defect #8551: Bulk edit leads to 404
- Etienne Massip wrote:
> Mirko, did you restart your server instance after you did revert the ApplicationHelper changes ?
Hi Etienne,
Yes I always do a full apache restart which restarts redmine as well. After doing this changes ma... -
15:54 Defect #8551: Bulk edit leads to 404
- Jérémy Chatard wrote:
> Here's my @issues.html.erb@.
It's fine too. Mirko, did you restart your server instance after you did revert the ApplicationHelper changes ?
> ...
Nope :/
-
15:22 Defect #8551: Bulk edit leads to 404
- Here's my @issues.html.erb@.
For the database, I _used_ to have some plugins which may have modified the database. Will need more time to check that, after work or tomorrow.
Any reason why one would try to load the @ProjectsControl... -
14:58 Defect #8551: Bulk edit leads to 404
- Etienne Massip wrote:
> I would be very surprised if this was a DB issue;
There was an earlier issue with bulk edits which was related to custom fields (see #7985) but this obviously doesn´t apply here. In my case the code is directl... -
14:39 Defect #8551: Bulk edit leads to 404
- I would be very surprised if this was a DB issue; could you post your @app/views/context_menus/issues.html.erb@ file too, please ?
-
14:02 Defect #8551: Bulk edit leads to 404
- Yes, the given file seems to be the bare 1.2-stable routes file. No differences found.
Did you or a plugin make any changes to your redmine database?
Mirko -
13:47 Defect #8551: Bulk edit leads to 404
- I don't know if this is an just an example, but you are on the @IssuesController@ where I'm on the @ProjectsController@.
By the way, here's my @config/routes.rb@ as an attachement to keep the thread readable. Please note that as far a... -
13:36 Defect #8551: Bulk edit leads to 404
- Jérémy Chatard wrote:
> I have absolutely no knowledge of the Redmine source code, but doesn't this look like an incorrect routing issue?
> ...
That kind of thing, yes.
You should get something like this : -
10:32 Defect #8551: Bulk edit leads to 404
- Etienne Massip wrote:
> @app/helpers/application_helper.rb@ might be relevant; try with bare one.
Thank you for your comment. I´ve reverted the file. I changed it while looking into that issue. Sorry for the confusion. Using the bare... -
09:25 Defect #8551: Bulk edit leads to 404
- *I have absolutely no knowledge* of the Redmine source code, but doesn't this look like an incorrect routing issue?
-
09:11 Defect #8551: Bulk edit leads to 404
- * No plugin, just Redmine
* Happens in every context I can find (i.e. always)
Just set log level to @:debug@ from @production.log@: -
13:41 Defect #8582 (Closed): RuntimeError (Your PostgreSQL connection does not support unescape_bytea. Try upgrading to pg 0.9.0 or later.)
- Setup issue.
-
13:20 Defect #8614 (Closed): Vice Presidet -> Vice Chairman
- Please use http://demo.redmine.org for testing purposes.
-
10:30 Defect #8614 (Closed): Vice Presidet -> Vice Chairman
- Det är tråkigt och konfunderande både för medlemmar och presidiet att ordet "ordförande" på bthstudent.se översätts olika i "Ordförande" och "Vice ordförande". Därför föreslår jag att "Vice Ordförande" blir "Vice chairman" istället för "...
-
13:20 Defect #8613 (Closed): Test1
- Please use http://demo.redmine.org for testing purposes.
-
10:07 Defect #8613 (Closed): Test1
-
13:18 Defect #8612: Custom Field Update gives Internal error
- Is your MySQL @journal_details.value@ column / table / db charset set to UTF-8 as it should ?
-
11:20 Defect #8612: Custom Field Update gives Internal error
- Hi Massip,
Production Log details are as follows:
Processing IssuesController#update (for 172.29.240.69 at 2011-06-15 14:47:51) [PUT]
Parameters: {"time_entry"=>{"comments"=>"", "activity_id"=>"", "hours"=>""}, "commit"=>"Su... -
09:11 Defect #8612: Custom Field Update gives Internal error
- What's the contents of the @production.log@ file relating to this error ?
-
07:34 Defect #8612 (Closed): Custom Field Update gives Internal error
- I have created a Custom Field with type "Long Text".
Trying to update the field with following text.
BPC=4Bitの場合、DLScreen情報用メモリ確保が必要か確認する処理が抜けている箇所があり、そのため無駄なメモリ確保を大量に行っていました。
これにより、指摘データ出力時はメモリ確保量が限界に達し、PCL6解析中にメモリ不足による内部エラーが発生し... -
13:12 Defect #8611 (Closed): rake/rdoctask is deprecated
- Not a redmine issue, just a rake/RoR compatibility warning.
-
04:20 Defect #8611 (Closed): rake/rdoctask is deprecated
- whenever I raked something(like, rake db:migrate), I got this warning:
-
12:08 Defect #8616 (Closed): Circular relations
- I think I found a bug in redmine, correct me if I'm wrong.
3 issues: 1, 2, 3
two cases:
# 1 blocked_by 2,3
2 blocks 1, blocked_by 3
3 blocks 1,2
# 1 blocks 3, blocked_by 2
2 blocks 1, blocked_by 3
3 blocks 2, blocked_by 1
... -
11:16 Defect #8615 (Closed): Custom 'version' fields don't show shared versions
- subj.
for fix i change in file @app\models\custom_fields.rb@: -
10:48 Defect #8573: Do not show inactive Enumerations where not needed
- Many thanks for your fix.
-
09:14 Feature #8606 (Closed): Payroll Log Color Peak Payroll Client
- Not the good issue tracker.
-
09:14 Feature #8609 (Closed): FPS FAIL in 0.38.37
- Not the good issue tracker.
-
02:49 Feature #8609 (Closed): FPS FAIL in 0.38.37
- maps like flatsville county by brickman have fps lower then 3 when i look across the map i get 1 fps which is horrible i have the file edited by brickman the fps.terrn file which is the same terrn file but with less stuff i have deleted ...
-
09:13 Defect #8608 (Closed): beacons in 0.38.37
- Not the good issue tracker.
-
02:34 Defect #8608: beacons in 0.38.37
- anyone know of this problem
i need tdev to do this -
02:30 Defect #8608 (Closed): beacons in 0.38.37
- when i get in the cormac gritter if i turn the beacons on they work but if i spawn another and turn them on get out the cormac i just got out of the beacons will stay on in that but the other cormacs beacons turn off
-
07:16 Defect #7688: Redmine's trunk (rails 2.3.11) doesn't work with Mongrel 1.1.x
- bo ye wrote:
> We use patch_for_mongrel.rb and mongrel.rb together, it is fine for now.
> ...
I am running now Redmine 1.2.0 and use mongrel.rb only and it seems all is OK. I never tried to see what would happen if both patches are in. -
03:23 Defect #7688: Redmine's trunk (rails 2.3.11) doesn't work with Mongrel 1.1.x
- We use patch_for_mongrel.rb and mongrel.rb together, it is fine for now.
Ivan Cenov wrote:
> "Most Active This Week":http://rubyforge.org/top/mostactive.php?type=week shows 96.90% activity.
> ...
-
00:34 Defect #8607 (Closed): problem for installing RedMine1.2
- Here is my environment:
2011-06-14
-
23:31 Defect #8325: undefined method `name' for "actionmailer":String (RubyGems > 1.6 not supported)
- Also got bit by this while upgrading Redmine to 1.2.0.
That bug hasn't been fixed for over a month now. Now, I can't even go back to 1.1.3. -
22:37 Feature #8606 (Closed): Payroll Log Color Peak Payroll Client
- Create colored records for Peak Payroll clients in payroll log for easier identification.
-
19:49 Defect #8551: Bulk edit leads to 404
- @app/helpers/application_helper.rb@ might be relevant; try with bare one.
-
17:43 Defect #8551: Bulk edit leads to 404
- Thank you for your help. I´ve removed all plugins from the plugins directory and restarted the server (now redmine shows that there are no plugins installed). Since I we use redmine from svn (1.2-stable) I´ve checked the status of all re...
-
17:12 Defect #8551: Bulk edit leads to 404
- In a parent project issues list selecting issues from subprojects...
-
17:11 Defect #8551: Bulk edit leads to 404
- I'm sorry, I tried in different ways but didn't reproduce on 1.2.0 ; if you use plugins then disable them, try again and let us know, please.
If no plugins, please give more details : does this happen systematically, from every issues l... -
15:10 Defect #8551: Bulk edit leads to 404
- Please could somebody take a look at this issue. Its still not solved. I would happily provide all info necessary to track this down. I´ve full access to the server and can easily reproduce this error.
Every hint is welcome!
Thanks... -
17:37 Defect #8603: Query 'without subprojects' cannot be created
- Confirmed, there is a strange behavior here :
If you add the subproject filter then save the query with "all projects" checked, the filter won't be saved.
If you add the subproject filter then save the query leaving "all projects" ... -
13:54 Defect #8603 (New): Query 'without subprojects' cannot be created
- I wanted a global, public query that sets 'subproject' to 'none'.
Does work in a project, but cannot be saved.
Reason seems to be, that the query option is only available if subprojects exist.
The code that deletes it when saving ... -
17:16 Feature #8145: API: Redmine version
- Switched with #5901.
-
16:13 Feature #4796: Rails 3 support
- Fabian Becker wrote:
> It's becoming a pain maintaining Redmine as it currently is.
Can't see why ?
-
16:00 Feature #4796: Rails 3 support
- Is there any update on migrating to Rails 3.x? It's becoming a pain maintaining Redmine as it currently is. Upgrading to 3.0/3.1RC would definitely improve the development process.
I do understand that you are having trouble loosing c... -
15:12 Defect #8605 (Closed): 测试系统
- Please use http://demo.redmine.org for testing purposes.
-
15:05 Defect #8605 (Closed): 测试系统
- 需要注册帐号,然后测试系统的性能
-
14:57 Defect #8604 (Closed): Parent task progress depends on children tasks
- Very inconvenient defect.
When i have a task for developer and subtask for designer i need a different displaying ready-progress. But in current version i can't understand is task ready or not, because if designer set subtask option ... -
13:08 Defect #4610: undefined method `env_table' for nil:NilClass (NoMethodError) with rev 3335
- I was able to get redmine 1.2.0 working with cgi with the following patch to rails:
-
12:52 Defect #8539: Fix NoMethodError in Issue#blocked? due to invalid issue_from_id in Issue#relations_from
Result is..-
11:47 Defect #7857: A NoMethodError occurred in account#login
- Dmitry Salashnik wrote:
> for solving my problem i put rails_6440_patch.rb to @config\initializers@ folder and my problem is gone...
I just did the same and it fixed my problem. Thanks Dmitry. -
08:08 Defect #7857: A NoMethodError occurred in account#login
- for solving my problem i put rails_6440_patch.rb to @config\initializers@ folder and my problem is gone...
-
08:38 Defect #8602 (Closed): I cant see one of my projects repository......it shows internal error
- My svn and redmine is working good and all projects and repository also good...
but only when i open one of my project's repository it shows
--------------
*Internal error*
An error occurred on the page you were trying to access... -
07:13 Defect #8583: Proxy Error The proxy server received an invalid response from an upstream server.
- I try to install rake, doing like in instruction:
cd C:\webserver\Redmine
set RAILS_ENV=production
rake generate_session_store
rake db:migrate
The line - "rake generate_session_store" give me some warning:
'task :t, arg, :needs =... -
06:07 Defect #8601 (Closed): Assignee didn't receive email notification
- Actually there has two bugs here:
# No matter what I select from the User config Email Notification, it always show back 'For any event of all my projects'
# If I assign a ticket to a user, the assignee don't receive any email, but t... -
05:46 Feature #5638: Use Bundler (Gemfile) for gem management
- I pushed my github repository branch.
https://github.com/marutosi/redmine/commits/redmine-bundler -
04:42 Defect #8600 (Closed): Encoding::CompatibilityError in Welcome#index
- Redmine does not support Ruby 1.9, now.
Try #4050 patches. -
04:36 Defect #8600 (Closed): Encoding::CompatibilityError in Welcome#index
- redmine 1.2.0
Encoding::CompatibilityError in Welcome#index
Showing app/views/layouts/base.rhtml where line #64 raised:
incompatible character encodings: UTF-8 and GBK
Extracted source (around line #64):
61:
62: <... -
00:09 Defect #5089 (Resolved): i18N error on truncated revision diff view
- Fixed in r6073.