Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.

    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support

    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?
      Create a new account

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
  • Roadmap
  • Work packages
  • Calendars
  • Team planners
  • Boards
  • Forums
  • Wiki
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showDeveloper
        • Hierarchy leafAccessibility Checklist
        • Hierarchy leafCode Review Guidelines
        • Expanded. Click to collapseCollapsed. Click to showContribution
          • Hierarchy leafGit Workflow
          • Hierarchy leafTranslations
        • Expanded. Click to collapseCollapsed. Click to showDeveloping Plugins
          • Hierarchy leafDeveloping an OmniAuth Authentication Plugin
        • Hierarchy leafRelease Process
        • Hierarchy leafReport a bug
        • Hierarchy leafSecurity
        • Hierarchy leafSetting up an OpenLDAP server for testing
        • Hierarchy leafTheme Features
      • Hierarchy leafDownload
      • Expanded. Click to collapseCollapsed. Click to showFeature tour
        • Hierarchy leafRelease Notes OpenProject 30
        • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 30 - Overview
          • Hierarchy leafGlossary
          • Hierarchy leafRelease Notes - Accessibility
          • Hierarchy leafRelease Notes - Accessibility changes
          • Hierarchy leafRelease Notes - Add work package queries as menu items to sidebar
          • Hierarchy leafRelease Notes - Copy projects based on Templates
          • Hierarchy leafRelease Notes - Design changes
          • Hierarchy leafRelease Notes - Fixed Bugs
          • Hierarchy leafRelease Notes - Keyboard Shortcuts
          • Hierarchy leafRelease Notes - Project settings
          • Hierarchy leafRelease Notes - Ruby&Rails Update
          • Hierarchy leafRelease Notes - Security
          • Hierarchy leafRelease Notes - Timelines
          • Hierarchy leafRelease Notes - Work packages
      • Hierarchy leafHowto create animated gifs
      • Hierarchy leafMigration Squashing
      • Hierarchy leafMod security
      • Hierarchy leafNew work package page
      • Hierarchy leafOP3 to OP4 Debian upgrade
      • Hierarchy leafOP4 Ubuntu1404 Stable with MySQL in production
      • Hierarchy leafOpenProject 40 Development Setup
      • Expanded. Click to collapseCollapsed. Click to showOpenProject Foundation
        • Hierarchy leafBoards
        • Hierarchy leafMembers
        • Hierarchy leafOPF-Meetings
        • Hierarchy leafStatutes
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes
        • Hierarchy leafOpenProject released on Bitnami
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 40 - Overview
        • Hierarchy leafRelease Notes OpenProject 40 - Accessibility improvements
        • Hierarchy leafRelease Notes OpenProject 40 - Column header functions in work package table
        • Hierarchy leafRelease Notes OpenProject 40 - Improved Design
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated query title on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated toolbar on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - OmniAuth integration for OpenProject
        • Hierarchy leafRelease Notes OpenProject 40 - Work package details pane
      • Expanded. Click to collapseCollapsed. Click to showSecurity and privacy
        • Hierarchy leafFAQ
      • Expanded. Click to collapseCollapsed. Click to showSupport
        • Expanded. Click to collapseCollapsed. Click to showDownload and Installation
          • Hierarchy leafInstallation MacOS
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 3 0
            • Hierarchy leafDebian Stable with MySQL in production
            • Hierarchy leafInstallation Ubuntu
            • Hierarchy leafInstallation Windows
            • Hierarchy leafInstallation on Centos 65 x64 with Apache and PostgreSQL 93
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 40
            • Hierarchy leafOP4 Debian Stable with MySQL in production
          • Expanded. Click to collapseCollapsed. Click to showMigration paths
            • Hierarchy leafFrom Chilliproject to OpenProject
            • Hierarchy leafMigration 15 to 30
            • Hierarchy leafMigration 24 to 30
            • Hierarchy leafMigration Redmine 2x › OpenProject 30
            • Hierarchy leafOpenProject 3 Migration
          • Hierarchy leafOpenProject 40
        • Expanded. Click to collapseCollapsed. Click to showNews
          • Hierarchy leafNew OpenProject Translations Plugin
          • Hierarchy leafNew Plugin on OpenProjectorg Local Avatars
          • Hierarchy leafNew design for OpenProject
          • Hierarchy leafNews Accessibility workshop for OpenProject
          • Hierarchy leafNews Glossary for OpenProject
          • Hierarchy leafNews Heartbleed fixed
          • Hierarchy leafNews Icon Fonts
          • Hierarchy leafNews OpenProject 30 Release
          • Hierarchy leafNews Release GitHub Integration Plugin
          • Hierarchy leafNews Success Story Deutsche Telekom
          • Hierarchy leafNews Timelines
          • Hierarchy leafOpenProject 3013 released
          • Hierarchy leafOpenProject 3017 released
          • Hierarchy leafOpenProject 40 released
          • Hierarchy leafOpenProject 40 will be coming soon
          • Hierarchy leafOpenProject 405 released
          • Hierarchy leafOpenProject and pkgrio
          • Hierarchy leafOpenProject news moved to a new blog
          • Hierarchy leafOpenProjectBitnami
          • Hierarchy leafPackager version with plugins released ("Community edition")
          • Hierarchy leafRegistration OpenProject-Foundation
          • Hierarchy leafRelease OpenProject AuthPlugins
          • Hierarchy leafUpdates on OpenProject
          • Hierarchy leafWe need your feedback for the the new fullscreen view for work packages
        • Hierarchy leafOpenProject Plug-Ins
      • Hierarchy leafWiki
You are here:
  • Forums
  • General discussion

Content

Total database scramble?

Added by Yadin Flammer almost 6 years ago

I’m attempting to find any assistance to fix and keep using this product as development has claimed this behavior is not a bug and offered no help as a result. The system appears to have suffered a serious bug at some point, but as the claim is no one else has this issue we can call the bug a random self corruption of the database.

The problem is, any comment added to any package in any project results in this entry every time that lists all kinds of bizarre changes that were not actually made. Looking at the details of these false changes shows they reflect attributes of deleted packages from deleted projects. Some times it’s falsely showing the package has been turned into a deleted package (it has not), some times it shows one deleted package turned into another deleted package with no reflection of the actual package. In all cases the information shown is still fine, it’s just the change record is complete garbage, which is extremely confusing and muddy to look at, and means you have no clear indication of work changes at all, and the change emails sent are total nonsense. The easiest way to see this is in the details of the description change it claimed happened but didn’t (in no case what the description changed at all, despite the change record claiming total fiction happened).

The theory is that when a project is deleted, OP is failing to clean the database. It is then further failing to simply update rows in the database when a package is updated, but rather is copying the data to a new record instead (which would be highly inefficient due to how we know MySQL bloats databases if there were no rows to reuse). Further, it is then using the data in the target row to calculate the changes (although this fails to explain the 3 record mess in some cases) instead of just looking at the source and destination changes of the actual package. In other words, a serious bug in the software, but again development has rejected that this is happening in any way.

We’re hoping someone can offer ideas on how to clean this up, otherwise we will have to conclude the product is not usable at this time.


Replies (4)

RE: Total database scramble? - Added by Niels Lindenthal almost 6 years ago

Hi Yadin,

it is a quite unfriendly behavior. That makes me really angry.

There are very many people that spend a lot of their time to develop this great open source software. You never contributed in any kind to this open source project but blaming other people for not providing your free support? Sad.

My advice is pretty simple: If you want free support from anybody I suggest to start with saying something nice, e.g. “Thank you for building this software” and “I have not really a lot of experience in operating web applications but please can somebody help me?”.

Best
Niels

RE: Total database scramble? - Added by Yadin Flammer almost 6 years ago

My trying to get help when you refused makes you angry? I logged a bug and you dismissed it entirely, that makes me really frustrated. When I appealed that action you simply deleted the bug ticket entirely. I therefore came here to try to see if anyone would help since you obviously would not.

I have not contributed code, but in the past I have logged issues and assisted in their correction. If you don’t consider that helping, that’s what is sad. You only want to help people who write code for the product? Not a good model.

I have a lot of experience operating web applications, this one is broken. If you’re too good to try to address a crippling product bug unless the person shows deference I can only hope someone else on the team will assist, and address your extreme lack of customer service with you. It is a very nice free product IF it works, which currently it does not, which makes it a pile of unusable code. I’d like to help remedy that if someone is willing to address the problem. If you expect users to code their own bug fixes now, again that does not make for a usable product in general.

RE: Total database scramble? - Added by Yadin Flammer almost 6 years ago

In trying to figure out where OP is going wrong with the scrambled data, I have looked through the database tables and only come up with more mystery. There is clearly another place where data is being stored as the values in the web UI include things that are simply not in the database. I tried digging through the application directories but couldn’t find anything telling, although it’s extremely weird that it would be storing data records in flat files rather than keeping them all in the database.

Relations of work_packages to project_id is obvious. However the relation of work_packages to work_package_journals is not. When you look at a package in the UI and see the changes listed in activity include things that are not in either of those tables, I can’t divine where those are kept or where the relations are happening. When you then look at the details of a description change that didn’t happen, it shows you half what is in the work_package_journals entry, and half some other mystery information that is in neither table. Since I can’t track the relations or find the other data that it’s pulling out of seemingly nowhere to make these anomalous entries, I can’t troubleshoot this bug any further. Hopefully a developer will be able to track this down so the product can be fixed.

RE: RE: Total database scramble? - Added by Yadin Flammer almost 6 years ago

Problem persists in 6.1.5. Product is unusable while every comment in it creates a dozen bogus change records.

  • (1 - 4/4)
Loading...