Suitecrm: Subpanel column order is changed when i click next

Created on 27 Apr 2017  路  13Comments  路  Source: salesagility/SuiteCRM


Issue


When i click next in subpanel of modules, the order of column is changed.

Before
screenshot_2
After
screenshot_3

Expected Behavior


Column order should be same.

Actual Behavior

Possible Fix

Steps to Reproduce


  1. Open any module
  2. Look at subpanel, it should be content more than 10.
  3. Click next for other page
  4. Look at the differences between first page and second page

Context


Your Environment

  • SuiteCRM Version used: 7.8.3
  • Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Chrome latest
  • Environment name and version (e.g. MySQL, PHP 7): PHP 7
  • Operating System and version (e.g Ubuntu 16.04): Ubuntu 16.04
  • Theme: Suite7

Most helpful comment

@Dillon-Brown, @daniel-samson, This issue has been marked as closed but the bug is still there and impacting LTS now for several months (e.g. we are on Suite 7 theme, v7.8.8 LTS). This heavily impacts usability of SuiteCRM on Suite 7 theme, as user has to reload the page after each history-page-next, in order to be able to clearly see the record's history.

There seems to be a lot of ping-pong on this thread. @ale26 says he has proposed a solution, but it was not accepted. Please reopen and move this bug to the correct thread/branch, so it can be picked up and solved in the LTS branch.

All 13 comments

@dursuntosun I'm unable to replicate this on 7.8.3. The column order remains the same. Have you tried clearing the cache and repair/rebuild or replicating with a fresh instance?

After applying this fix, it is occured.
Fixed #3355

Hi,
Why did you close it? The problem is continue:(

@dursuntosun Ah sorry I might have misunderstood. Are you saying that the issue was caused by #3356 or that its still present before and after applying the fix?

There are no this issue before applying #3355. After applying this fix, it occurs.

@dursuntosun If the issue is a result of the proposed fix for #3355 then this wouldn't be a core SuiteCRM issue. You'll need to raise it with the creator of the fix @ale26 in #3356

I'm sorry for a lot of commits. They are all the same
There really only 1 commit. There was a problem with github, the commit was from another email address and the clahub did not accept this commit

The error did not occur due to damage to the HTML structure (Issue #3355). After fixing the HTML structure was shown error #3467.

At the global level, the error lies in the fact that the SuiteP library uses the footable library. This library should not work in Suite7 and SuiteR, but this fix does not take this into account. After applying this library in Suite7 and SuiteR - it breaks the order of the columns.

Do not forget to restore and rebuild and clear your browser's cache

Has this fix been propagated to 7.8.8 LTS branch? We still seem to be experiencing this 'pagination columns misalignment' issue in 7.8.8 on Suite 7 theme.

I fixed these errors, and created a pull request

But the developers modified my Pull-regest in such a way that the error was not corrected
( pull request )

The developers asked to check, I checked, wrote about the fact that their option will not work.

To date, the problem remains open and there is no desire to make changes again. Tickets are not considered for a very long time, often the new kernel code breaks existing functionality. I decided to give up SuiteCRM in my projects.

I will give the decision within 2 days...

@Dillon-Brown, @daniel-samson, This issue has been marked as closed but the bug is still there and impacting LTS now for several months (e.g. we are on Suite 7 theme, v7.8.8 LTS). This heavily impacts usability of SuiteCRM on Suite 7 theme, as user has to reload the page after each history-page-next, in order to be able to clearly see the record's history.

There seems to be a lot of ping-pong on this thread. @ale26 says he has proposed a solution, but it was not accepted. Please reopen and move this bug to the correct thread/branch, so it can be picked up and solved in the LTS branch.

@evgu, New pull request with fix error proposed. After accepting, the problem should go away

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Mausino picture Mausino  路  3Comments

Mausino picture Mausino  路  3Comments

darouca picture darouca  路  3Comments

ajprouty87 picture ajprouty87  路  3Comments

ArturoBurela picture ArturoBurela  路  3Comments