[ZBX-864]  Bug when editing a screen Created: 2009 Apr 15  Updated: 2017 May 30  Resolved: 2009 Apr 15

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 1.6
Fix Version/s: 1.6

Type: Incident report Priority: Major
Reporter: Artem Suharev (Inactive) Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

how to reproduce)
"Create Screen" on Configuration/Screens window
Name: EmptyScreenTest
Columns: 1
Rows: 1
Select "Edit" in "EmptyScreenTest"
Select "Change"
Select just "Save" without set "Graph name"

  1. refer to 1st attached image
    You can see "Item added" and "ERROR: No permission!"
  2. refer to 2nd attached image
    Additionally, this garbage data(screenitemid=3) is stored into "screens_items" table.
    Quote:
    mysql> select * from screens_items;
    ----------------------------------------------------------------------------------------------------------+
    screenitemid screenid resourcetype resourceid width height x y colspan rowspan elements valign halign style url dynamic

    ----------------------------------------------------------------------------------------------------------+

    2 2 2 2 0 0 0 0 2 0 0 0 0 0   0
    3 3 0 0 500 100 0 0 0 0 0 0 0 0   0

    ----------------------------------------------------------------------------------------------------------+
    2 rows in set (0.00 sec)
    I investigated a little. I think the cause is validation check in "screenedit.php". The $_REQUEST["resourceid"] hasn't checked(it's set zero) when we try to save screen cell. After that, we get error since it cannot find "resourceid".
    We should check whether $_REQUEST["resourceid"] has a value configured from "Resource".

http://www.zabbix.com/forum/showthread.php?p=44940



 Comments   
Comment by Artem Suharev (Inactive) [ 2009 Apr 15 ]

Fixed. rev. 7174

Comment by richlv [ 2009 Sep 15 ]

closing all resolved issues

Generated at Fri Apr 04 21:39:27 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.