mantisbt/mantisbt

Mantis Bug Tracker (MantisBT)

luzpaz

@luzpaz

(in MantisBT)

Roland Becker

@atrol

Doesn't work, see https://mantisbt.org/bugs/view.php?id=24883

brickviking

@brickviking

Okay. One last question (at least for now): how do I change the default collation for most of the tables? Under phpMyAdmin, most of those tables are showing up as latin1_swedish_ci

brickviking

@brickviking

And under that, phpMyAdmin shows a number of potential candidates for utf8mb4, from utf8mb4_bin to utf8mb4_vietnamese_ci.

Damien Regad

@dregad

This is standard mysql stuff, use appropriate ALTER TABLE statements (Google the details). Make sure to not only change the tables, but also the columns.

brickviking

@brickviking

I was wondering that, okay. Thank you.

Does the collation ever turn up in a mysqldump?

Damien Regad

@dregad

What do you mean, turn up ?

brickviking

@brickviking

If I do a "mysqldump -u <user> -p bugtable > bugtable.sql", I don't see any statements setting the collation.

Damien Regad

@dregad

It does for me

CREATE TABLE xxx (
...
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

brickviking

@brickviking

Yes, I get charset, but I don't get collate statements

Is that inferred from the charset?

Damien Regad

@dregad

TBH I don't know. Check the mysql docs I guess.

brickviking

@brickviking

I think I managed it: phpMyAdmin has a way to change the collate settings for the database as a whole, including table and table column collation.

And the sql query "succeeded".

Damien Regad

@dregad

cool

brickviking

@brickviking

Is there a reason to prefer InnoDB or MyISAM? My db seems to have its tables all defined as MyISAM, but the DB itself says it's InnoDB

Damien Regad

@dregad

MyISAM is a more simple engine with limited support for transactions, InnoDB is more modern as became MySQL default a few years back. You can switch if you want

brickviking

@brickviking

hm, okay. I seem to be asking questions that aren't exactly specific to Mantis...sorry about that, but I know sod all SQL.

but boy have I got used to the "mysql" commandline client.

Damien Regad

@dregad

lol

brickviking

@brickviking

ugh. And now a stray cup of tea has killed another fine keyboard.

brickviking

@brickviking

and trying to find another Logitech K750 for reasonable price is ... well, it isn't happening.

brickviking

@brickviking

Thankfully, it looks like the K750 has "dried out" sufficiently to not be causing issues any more. Phew.

brickviking

@brickviking

I'm having some issues with modifying users, and I keep getting a "APPLICATION ERROR #2800", or "Invalid form security token" error if I try to alter a user's details from within Mantis. Any known problems around this?

I can modify the details from the back end (using the mysql client) without any errors, of course.

In addition, I notice that the github repo doesn't contain ANY issues.

brickviking

@brickviking

The issue appears here: ${webroot}/mantis/manage_user_edit_page.php?user_id=<userID>, and selecting a different access level, (and turning off <email user on change> because we haven't got email set up yet), and selecting Update User results in what I posted before (Application error 2800)

Damien Regad

@dregad

Did you read https://mantisbt.org/docs/master/en-US/Admin_Guide/html-desktop/#admin.troubleshooting.errors.2800

Does this happen systematically ? With other edit pages too ? Right after loading the page, or after some delay ?

the github repo doesn't contain ANY issues.

Why should it ? Mantis is a bug tracker, and logically we use our own product to track defects :wink:

luzpaz

@luzpaz

how does mantis output to a log file? Where in the code is an example of this ?

Damien Regad

@dregad

~/dev/mantisbt(master) $ git grep -w log_event

brickviking

@brickviking

Basically, it seems to croak directly on loading the page AFTER I click the "Update User" button, within a couple of seconds. I don't know if that's because of being on a remote host or not.

brickviking

@brickviking

Okay, some more info: session.gc_probability = 0; and session.gc_maxlifetime = 1440; I suspect that means GC isn't happening.

brickviking

@brickviking

On my local host, the issue doesn't happen, at least if I take less than 24 minutes to make up my mind. But there, the probability is gc_probability = 1 (not 0). So I get the expected result, and 2800 after 24 minutes, as I should.

brickviking

@brickviking

I finally had to clear my local cookies for bugs.myhost.here before the error would go away, yet for all four of those cookies, they're supposed to be removed when the session is closed.

I'm glad I read the relevant bug before I posted, I could have felt rather stupid

brickviking

@brickviking

Ahh, and I finally found the tracker for mantisbt itself. In the Admin guide.

Marc-Antoine TURBET-DELOF

@maturbet

Are any ones interested in testing this plugin ?
https://github.com/Association-Cocktail/QuietChangeStatus

Dale Mason

@Expression93_gitlab

I'm getting some sort of bizarre issue with uploads on my MantisBT install, I've had 2.22.0 running for months and nothing ever been changed, I just updated to 2.24.1 to try fix my issue but still encounter the same problem. It is to do with file downloads, older uploads that have a certain pattern to the binary data in the BLOB field all give errors (do not load inline on page and when downloaded just error in image viewers).

Xavi Montero

@xmontero

Hi all, new here. Just joining. I've been user of mantis for over 15 years. Since 2003 at least! Still using it.

(not the same version, though :D hahaha)

Damien Regad

@dregad

Welcome @xmontero

@Expression93_gitlab the information you provide is too vague to get an idea of what could be happening.

Dale Mason

@Expression93_gitlab

@dregad I ain't sure how else to explain it, as far as I am concerned nothing about my setup changed, it's been the same for weeks. Files uploaded by any user up to a certain point are now broken, when the file is downloaded (as it's supposed to be an image) it cannot be read in an image viewer (it just gives an error). Newer uploads appear to work fine, but these problematic file uploads would have worked at the time (otherwise we'd have noticed the issue sooner). The only difference I can see is that the BINARY data changes, all the broken files start with the same data, and they're all broken, if I try the first file where that data changes, the download is fine. (For the record though, the data is still unique for all of those problematic files)

Damien Regad

@dregad

@Expression93_gitlab if I understand correctly, you had a 2.22 instance working perfectly, then you started noticing corrupted attachments and you tried upgrading to 2.24.1 to fix it but it didn't ? If so, everything else being equal, I would say that excludes MantisBT from being the problem's root cause...

Since you mention BLOB field, I assume you're storing attachments in the DB (as opposed to file system). Maybe some corruption on the database ?

When I say "too vague" you mention bizarre issue, certain pattern, errors etc. Nothing specific that anyone could objectively use to analyze and try to find out what the problem is.

Benjamin

@benjamin86

any dev using vs code and able to make the format to follow the mantisbt coding guideline?
my vs code will format One space after the opening ( and before the closing )
and change comment # to //

Where communities thrive

People

Repo info

Activity