View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0022752 | mantisbt | performance | public | 2017-04-20 15:53 | 2018-01-14 13:53 |
Reporter | vits_soporte | Assigned To | atrol | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Product Version | 2.3.1 | ||||
Summary | 0022752: Status icons change to black | ||||
Description | Hello, according to attached graphs, when you press repeatedly on menu options, the status icons change to black as well as finally says | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
vits_soporte, I was not able to reproduce your problem with a fresh install of MantisBT release. The following additional information may be useful:
|
|
Hi, I really Thank you for the answer: A) php vrs 5.5 | Bd mysql (mysql) | Apache | Chrome, firefox, ie | Windows 8 1 ) when would you release vrs 2.3.2? Thanks for the support, Atn: Carlos Felipe Lozada |
|
Hi, And an additional question, is some plugin or configuration, to be able to visualize images in the notes of the .jpg attachments? thanks. Atn: Carlos Felipe |
|
Hello, attachment for chrome, debugging in case this is anything, highlighting that we have not made any modification in these files Thank you for all the support you can give us Atn: Carlos Lozada |
|
There is certainly some more information behind the red marked GET in browser console. Check also your web server / PHP logs for errors and warnings. |
|
Hello Astrol, thanks for the reply, could you please help us? We are attaching the warnings and errors we have created from scratch the vrs 2.3.0 and you can enter: www.hqo.sgep.venturitsoft.com/mantisbt-2.3.0/ "login.jpg" logs for errors : [Sun Apr 23 15:48:39.829088 2017] [:error] [pid 574353:tid 140483523233536] (12)Cannot allocate memory: [client 181.53.217.203:52417] couldn't create child process: /opt/suphp/sbin/suphp for /home/venturit/public_html/_proyecto/hqo-sgep/mantisbt-2.3.0/css/status_config.php, referer: http://www.hqo.sgep.venturitsoft.com/mantisbt-2.3.0/my_view_page.php Could you give us some new guidance? Why do you think refreshing the page sometimes looks good color and sometimes does not load css / status_config.php styles? And other times yes load? Thanks common_config.php (2,426 bytes)
<?php # MantisBT - A PHP based bugtracking system # MantisBT is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 2 of the License, or # (at your option) any later version. # # MantisBT is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with MantisBT. If not, see <http://www.gnu.org/licenses/>. /** * Generate Common CSS that requires PHP Output, and therefore can not be included in the .css files * For example, language specific settings * * @package MantisBT * @copyright Copyright 2000 - 2002 Kenzaburo Ito - kenito@300baud.org * @copyright Copyright 2002 MantisBT Team - mantisbt-dev@lists.sourceforge.net * @link http://www.mantisbt.org * * @uses config_api.php */ # Prevent output of HTML in the content if errors occur define( 'DISABLE_INLINE_ERROR_REPORTING', true ); @require_once( dirname( dirname( __FILE__ ) ) . '/core.php' ); require_api( 'lang_api.php' ); require_api( 'config_api.php' ); /** * Send correct MIME Content-Type header for css content. */ header( 'Content-Type: text/css; charset=UTF-8' ); /** * Don't let Internet Explorer second-guess our content-type, as per * http://blogs.msdn.com/b/ie/archive/2008/07/02/ie8-security-part-v-comprehensive-protection.aspx */ header( 'X-Content-Type-Options: nosniff' ); $g_display_errors = null; /** * WARNING: DO NOT EXPOSE SENSITIVE CONFIGURATION VALUES! * * All configuration values below are publicly available to visitors of the bug * tracker regardless of whether they're authenticated. Server paths should not * be exposed. It is OK to expose paths that the user sees directly (short * paths) but you do need to be careful in your selections. Consider servers * using URL rewriting engines to mask/convert user-visible paths to paths that * should only be known internally to the server. */ ?> div.form-container fieldset.required:after { position: absolute; margin: -1.75em 0em 0em .5em; font-size: 8pt; content: '* <?php echo lang_get( 'required' ); ?>'; color: red; } config_inc.php (753 bytes)
<?php $g_hostname = 'localhost'; $g_db_type = 'mysqli'; $g_database_name = 'venturit_hqo-sgep-mantisbt-2'; $g_db_username = 'venturit_hqo'; $g_db_password = 'soporte-hqo'; $g_default_timezone = 'America/Bogota'; $g_crypto_master_salt = '7knF11nm7ssTSXR5kAthKk9Wm2eayEnynG7VgmyAT+E+'; //Cantidad de cajas de texto en el inicio, para simplificar la informaciĆ³n a mostrar $g_my_view_boxes = array ( 'assigned' => '1', #1 'unassigned' => '0', #2 'reported' => '0', #3 'resolved' => '0', #4 'recent_mod' => '5', #5 'monitored' => '0', #6 'feedback' => '0', #0 'verify' => '0', #0 'my_comments' => '0' #0 ); status_config.php (3,781 bytes)
<?php # MantisBT - A PHP based bugtracking system # MantisBT is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 2 of the License, or # (at your option) any later version. # # MantisBT is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with MantisBT. If not, see <http://www.gnu.org/licenses/>. /** * Generate CSS from that requires output from php for specific settings e.g. status values * * @package MantisBT * @copyright Copyright 2000 - 2002 Kenzaburo Ito - kenito@300baud.org * @copyright Copyright 2002 MantisBT Team - mantisbt-dev@lists.sourceforge.net * @link http://www.mantisbt.org * * @uses config_api.php */ # Prevent output of HTML in the content if errors occur define( 'DISABLE_INLINE_ERROR_REPORTING', true ); @require_once( dirname( dirname( __FILE__ ) ) . '/core.php' ); require_api( 'config_api.php' ); /** * Send correct MIME Content-Type header for css content. */ header( 'Content-Type: text/css; charset=UTF-8' ); /** * Don't let Internet Explorer second-guess our content-type, as per * http://blogs.msdn.com/b/ie/archive/2008/07/02/ie8-security-part-v-comprehensive-protection.aspx */ header( 'X-Content-Type-Options: nosniff' ); /** * WARNING: DO NOT EXPOSE SENSITIVE CONFIGURATION VALUES! * * All configuration values below are publicly available to visitors of the bug * tracker regardless of whether they're authenticated. Server paths should not * be exposed. It is OK to expose paths that the user sees directly (short * paths) but you do need to be careful in your selections. Consider servers * using URL rewriting engines to mask/convert user-visible paths to paths that * should only be known internally to the server. */ /** * @todo Modify to run sections only on certain pages. * eg. status colors are only necessary on a few pages.(my view, view all bugs, bug view, etc. ) * other pages may need to include dynamic css styles as well */ $t_referer_page = array_key_exists( 'HTTP_REFERER', $_SERVER ) ? basename( parse_url( $_SERVER['HTTP_REFERER'], PHP_URL_PATH ) ) : basename( __FILE__ ); switch( $t_referer_page ) { case 'login_page.php': case 'signup_page.php': case 'lost_pwd_page.php': case 'account_update.php': # We don't need custom status colors on login page, and this is # actually causing an error since we're not authenticated yet. exit; } $t_status_string = config_get( 'status_enum_string' ); $t_statuses = MantisEnum::getAssocArrayIndexedByValues( $t_status_string ); $t_colors = config_get( 'status_colors' ); $t_status_percents = auth_is_user_authenticated() ? get_percentage_by_status() : array(); foreach( $t_statuses as $t_id => $t_label ) { $t_css_class = html_get_status_css_class( $t_id ); # Status color class if( array_key_exists( $t_label, $t_colors ) ) { echo '.' . $t_css_class . " { color: {$t_colors[$t_label]}; background-color: {$t_colors[$t_label]}; }\n"; } # Status percentage width class if( array_key_exists( $t_id, $t_status_percents ) ) { echo '.' . str_replace( 'color', 'percentage', $t_css_class ) . " { width: {$t_status_percents[$t_id]}%; }\n"; } } # Status legend width class $t_color_count = count( $t_colors ); $t_color_width = ( $t_color_count > 0 ? ( round( 100/$t_color_count ) ) : 0 ); echo ".status-legend-width { width: $t_color_width%; }\n"; |
|
Seems this is no longer true, as the issue can also be reproduced on http://www.hqo.sgep.venturitsoft.com/mantisbt-2.3.0 which is 2.3.0
Seems this is no MantisBT issue, but an issue with your server (not enough memory) and/or your web server configuration. You could also try to use another PHP version. |
|
Many thanks Astrol, we will escalate the issue with our hosting provider.
Thank you so much |
|
I recommend to use a newer version.
Should be in 1-2 weeks, but this will hardly solve your issue.
This is a setting of the MantisBT Formatting core plugin that comes with a standard installation. vits_soporte, This is not a bug or feature request for MantisBT (you are asking for help on how to deal with problems of your operating emvironment and for help on customization). I am therefore resolving this issue as "no change required". Please use the forums to get support on customizing and using MantisBT (refer to http://www.mantisbt.org/support.php for links and further details). |
|
For the record, I saw the "black squares" once while browsing https://mantisbt.org/bugs from my phone (iOS / Safari) yesterday; things went back to normal after a refresh. |
|
Thank you very much, very valuable your help, regards. -- |
|
Hello, thank you very much for all the support and indeed, fine tuning with my hosting provider, we managed to prove that the problem was php memory that had been reinitialized on the server. The solution is that the variable is above 256MB We attach file "Solution_Memory_Php_MEMORY_LIMIT.jpg" for whom this information can be used. And we were looking at the administrator's documentation We did not find this information and therefore our recommendation that the manual be updated with this prerequisite so that there are no failures as illustrated in this ticket. Thanks and regards. -- |
|
Thanks @vits_soporte for this information. I am a bit astonished, as memory usage on my test system is just about 2-3MB. |
|
Got a hint in forum that might explain it, see http://www.mantisbt.org/forums/viewtopic.php?f=9&t=24870#p62899 |
|