This forum is no longer active. Please post your questions to our new community site

Forums Redmine

Proxy Error after upgrade to Redmine SVN trunk

Subscribe to Proxy Error after upgrade to Redmine SVN trunk 25 post(s), 9 voice(s)

 
Avatar Cord Schneider 12 post(s)

Hi all,

I had a working Windows Redmine BitNami stack that I attempted to upgrade to the Redmine SVN trunk by following a combination of these instructions: http://bitnami.org/article/how-to-backup-and-up…
and http://www.redmine.org/wiki/redmine/RedmineUpgrade

The upgrade appeared to go fine (no errors reported) and all services restarted correctly. However, when I attempt to access Redmine I receive the following error in the browser:


Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.

Reason: Error reading from remote server

As per several other threads on the forum I have tried to access http://127.0.0.1:3001 and http://127.0.0.1:3002 but don’t get a response in the browser. I can successfully telnet to these addresses so Mongrel is running and the firewall is not blocking access.

I have repeatedly tried restarting all the services, as well as separately restarting the Mongrel services. In all cases, I get the proxy error reported above.

My apache access.log looks like this:

192.168.0.85 – - [26/Jan/2010:10:26:50 +0000] “GET / HTTP/1.1” 502 379

My apache error.log looks like this:

[Tue Jan 26 10:26:00 2010] [notice] Apache/2.2.13 (Win32) configured — resuming normal operations
[Tue Jan 26 10:26:00 2010] [notice] Server built: Aug 6 2009 15:50:50
[Tue Jan 26 10:26:00 2010] [notice] Parent: Created child process 6024
[Tue Jan 26 10:26:00 2010] [notice] Child 6024: Child process is running
[Tue Jan 26 10:26:00 2010] [notice] Child 6024: Acquired the start mutex.
[Tue Jan 26 10:26:00 2010] [notice] Child 6024: Starting 64 worker threads.
[Tue Jan 26 10:26:00 2010] [notice] Child 6024: Starting thread to listen on port 80.
[Tue Jan 26 10:26:57 2010] [error] [client 192.168.0.85] (OS 10054)An existing connection was forcibly closed by the remote host. : proxy: error reading status line from remote server 127.0.0.1
[Tue Jan 26 10:26:57 2010] [error] [client 192.168.0.85] proxy: Error reading from remote server returned by /

And my mongrel.log looks like this:

** Starting Mongrel listening at 0.0.0.0:3001

  • Starting Rails with production environment…
    D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/depenD:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:440:in `load_missing_constant’: uninitialized constant ActionController::Session::PStore (NameError)
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:80:in `const_missing’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/session_management.rb:19:in `const_get’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/session_management.rb:19:in `session_store=’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:602:in `send’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:602:in `initialize_framework_settings’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:601:in `each’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:601:in `initialize_framework_settings’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:598:in `each’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:598:in `initialize_framework_settings’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:155:in `process’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:113:in `send’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:113:in `run’
    from D:/BitNami Redmine Stack/apps/redmine/config/environment.rb:20
    from D:/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:147:in `rails’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:113:in `cloaker_’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:149:in `call’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:149:in `listener’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:99:in `cloaker_’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:50:in `call’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:50:in `initialize’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:84:in `new’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:84:in `run’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/command.rb:212:in `run’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281
    from D:/BitNami Redmine Stack/ruby/bin/mongrel_rails:19:in `load’
    from D:/BitNami Redmine Stack/ruby/bin/mongrel_rails:19
  • Starting Mongrel listening at 0.0.0.0:3002
  • Starting Rails with production environment…
    D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/depenD:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:440:in `load_missing_constant’: uninitialized constant ActionController::Session::PStore (NameError)
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:80:in `const_missing’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/session_management.rb:19:in `const_get’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/session_management.rb:19:in `session_store=’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:602:in `send’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:602:in `initialize_framework_settings’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:601:in `each’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:601:in `initialize_framework_settings’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:598:in `each’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:598:in `initialize_framework_settings’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:155:in `process’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:113:in `send’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:113:in `run’
    from D:/BitNami Redmine Stack/apps/redmine/config/environment.rb:20
    from D:/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:147:in `rails’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:113:in `cloaker_’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:149:in `call’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:149:in `listener’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:99:in `cloaker_’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:50:in `call’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:50:in `initialize’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:84:in `new’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:84:in `run’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/command.rb:212:in `run’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281
    from D:/BitNami Redmine Stack/ruby/bin/mongrel_rails:19:in `load’
    from D:/BitNami Redmine Stack/ruby/bin/mongrel_rails:19

As per http://www.redmine.org/wiki/redmine/RedmineInst… I also upgraded Rails to 2.3.5, and added Rack 1.0.1.

Can anyone shed some light as to what is going wrong?

 
Avatar Beltrán Rueda Administrator 3,714 post(s)

I can see the following in the Redmine Wiki (http://www.redmine.org/wiki/redmine/RedmineUpgr…

6. If upgrading to 0.8.7+ or 0.9+, run “rake config/initializers/session_store.rb”

Maybe this is your case.

 
Avatar Cord Schneider 12 post(s)

Nope, I doubt that’s the problem: I did run “rake config/initializers/session_store.rb” after the update as instructed. I also didn’t get any errors about a missing session_store.rb.

I think that the error has something to do with this line in the mongrel log:

D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/depenD:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:440:in `load_missing_constant': uninitialized constant ActionController::Session::PStore (NameError)

After the update, I added this line back into environment.rb (it was defined in the original Redmine stack):

config.action_controller.session_store = :PStore

I tried removing it and restarting the services but still no joy.

 
Avatar Cord Schneider 12 post(s)

Further investigation into PStore error indicates that the new update lacks the redmine/vendor/rails directory. I tried copying it over and now I get a different error: mongrel.log now informs me that “This version of the engines plugin requires Rails 2.3.2 or later!” which by all appearances is installed. I’ll try commenting out: RAILS_GEM_VERSION = ‘x.×.x’ unless defined? RAILS_GEM_VERSION

 
Avatar Cord Schneider 12 post(s)

That didn’t work either. The mongrel.log looks like this:

** Starting Mongrel listening at 0.0.0.0:3001

  • Starting Rails with production environment…
    D:/BitNami Redmine Stack/apps/redmine/config/../vendor/plugins/engines/boot.rb:4: This version of the engines plugin requires Rails 2.3.2 or later! (RuntimeError)
    from D:/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require’
    from D:/BitNami Redmine Stack/apps/redmine/config/environment.rb:15
    from D:/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:147:in `rails’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:113:in `cloaker_’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:149:in `call’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:149:in `listener’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:99:in `cloaker_’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:50:in `call’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:50:in `initialize’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:84:in `new’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:84:in `run’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/command.rb:212:in `run’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281
    from D:/BitNami Redmine Stack/ruby/bin/mongrel_rails:19:in `load’
    from D:/BitNami Redmine Stack/ruby/bin/mongrel_rails:19
  • Starting Mongrel listening at 0.0.0.0:3002
  • Starting Rails with production environment…
    D:/BitNami Redmine Stack/apps/redmine/config/../vendor/plugins/engines/boot.rb:4: This version of the engines plugin requires Rails 2.3.2 or later! (RuntimeError)
    from D:/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require’
    from D:/BitNami Redmine Stack/apps/redmine/config/environment.rb:15
    from D:/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:147:in `rails’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:113:in `cloaker_’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:149:in `call’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:149:in `listener’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:99:in `cloaker_’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:50:in `call’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:50:in `initialize’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:84:in `new’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:84:in `run’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/command.rb:212:in `run’
    from D:/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281
    from D:/BitNami Redmine Stack/ruby/bin/mongrel_rails:19:in `load’
    from D:/BitNami Redmine Stack/ruby/bin/mongrel_rails:19
 
Avatar Cord Schneider 12 post(s)

Does the Redmine stack come with some plugins pre-installed?

 
Avatar Beltrán Rueda Administrator 3,714 post(s)

Hi,

No, BitNami Redmine Stack does not ship any plugin.

 
Avatar Beltrán Rueda Administrator 3,714 post(s)

Please remove the vendor/rails folder. The application is taking the rails version that you copy in this folder.

 
Avatar Cord Schneider 12 post(s)

Surely the BitNami Redmine stack is expecting something in the vendor/rails directory? Or at the very least, if the vendor/rails directory is deleted, then the gems (?) that Redmine is expecting should be installed in the <install_dir>\ruby\lib\ruby\gems\1.8\gems directory..?

Sadly, I know nothing about how Ruby on Rails works – which is why I opted to use the BitNami stack because it is all configured for me. It looks like using the stack is fine so long as you don’t want to do anything to it (like update Redmine). :-S

 
Avatar Beltrán Rueda Administrator 3,714 post(s)

If you do not have any gems in the vendor, the application will search the gem in the default folder. The problem of the upgrades is that the application change their dependencies so it is necessary to install the dependencies too. Are you using the new “config/environment.rb” file or you are using the previous one?

 
Avatar Cord Schneider 12 post(s)

The old one … As per the instructions in http://bitnami.org/article/how-to-backup-and-up… I overwrote the contents of the new config/ with the contents of the old config/ although I did take care not to overwrite config/settings.yml as per the “VERY IMPORTANT” comment in http://www.redmine.org/wiki/redmine/RedmineUpgrade

Would the right way to do this simply be to copy the old config/database.yml and old config/email.yml into the update and leave the rest of the contents of config/ untouched?

 
Avatar darkol 1 post

Hi, any update.

I have run into same problem.

Thanks,
Darko

 
Avatar redm 2 post(s)

idem
cannot upgrade to 0.9.1
even after following instructions
http://www.redmine.org/wiki/redmine/RedmineUpgrade http://bitnami.org/article/how-to-backup-and-up…

 
Avatar Beltrán Rueda Administrator 3,714 post(s)

Hi all,

It is necessary to include the following fix for Mongrel to run with Rails 2.3.5. Please write a new file called “fixmongrel235.rb” in the apps/redmine/config/initializers folder and then restart the servers.


module ActionController
  class AbstractRequest < ActionController::Request
    def self.relative_url_root=(path)
      ActionController::Base.relative_url_root=(path)
    end
    def self.relative_url_root
      ActionController::Base.relative_url_root
    end
  end
end

I hope it helps.

 
Avatar lum 17 post(s)

I followed these instructions and now have .9.1 running. After a bunch of debuging, I checked my mongrel.log which mentioned that the mysql was outdated. I did a ‘gem install mysql’, which still returned the same error. I then copied the libmysql.dll from the mysql/bin directory to the ruby/bin directory, and things ‘just worked’.

 
Avatar snowrain 1 post

That did the trck. Thanks a lot

 
Avatar backlash79 4 post(s)

Hi all I’m trying to upgrade from 0.9.2 to 0.9.3 and initially got the proxy error, I ran the fixmongrel script posted above and was able to get to the login page again…however after submitting login information I get this page:

*
NoMethodError in Welcome#index

Showing app/views/welcome/index.rhtml where line #23 raised:

undefined method `cache_formatted_text?’ for #
Extracted source (around line #23):*

Any ideas? So far looking around I haven’t been able to find anything that helps.

 
Avatar skoub 7 post(s)

i get the same error. NoMethodError in Whelcome#index

ActionView::TemplateError (undefined method `cache_formatted_text?’ for #) on line #23 of app/views/welcome/index.rhtml:
20: <% for project in @projects >
21:


  • 22: <= link_to h(project.name), :controller => ‘projects’, :action => ‘show’, :id => project > (<= format_time(project.created_on) >)
    23: <
    = textilizable project.short_description, :project => project >
    24:

  • 25: < end %>
    26:

     
    Avatar Beltrán Rueda Administrator 3,714 post(s)

    Hi,

    This is a cache error. Try to clean your browser cache. Have you ran the following commands?

    $ rake tmp:cache:clear
    $ rake tmp:sessions:clear

     
    Avatar skoub 7 post(s)

    yes and i still have the error

     
    Avatar backlash79 4 post(s)

    I tried to clear the cache and still have the error as well.

     
    Avatar Beltrán Rueda Administrator 3,714 post(s)

    have you tried this fix? http://bitnami.org/forums/forums/redmine/topics…

     
    Avatar backlash79 4 post(s)

    Yes I did.

     
    Avatar blega 1 post

    Hello,

    I have to same issue cache_formatted_text.

    Any fix/workaround ??

    Cheers,
    B.

     
    Avatar backlash79 4 post(s)

    Has there been anything on this issue?

    Forums Redmine