<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Hi all,</div>
<div><br>
</div>
<div>Okay I'm stumped. I'm setting up a new install of RT4. My "proof of concept" install on a dev box was 4.0.6, but 4.0.10 was out by the time I got to setting up the "production" install, so that one is 4.0.10. The database for the 4.0.10 production system
was seeded with a dump from the 4.0.6 dev box. </div>
<div><br>
</div>
<div>When we create a new article class, none of the configuration options appear on the right hand side of /Admin/Articles/Classes/Modify.html. So, we can't make the new class apply to a queue. However, for the class that I created on the 4.0.6 system (I
then copied over the database to the "prod" install), the config options appear normally.</div>
<div><br>
</div>
<div>All of the users who are attempting to set up the classes have SuperUser privs.</div>
<div><br>
</div>
<div>Am I just missing something obvious, or did I trip on a bug in 4.0.10? Or, is there somewhere I can be looking to figure out what's going on? I can't see any differences in the databases that would be an obvious source of the differential behavior, and
a debug log doesn't spit out anything telling that I can see.</div>
<div><br>
</div>
<div>
<div>
<div>
<div>Any insight would be appreciated, including RTFM directives with helpful pointers to the correct FM, if I simply failed to find the right clue that's out there somewhere.</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>-- </div>
<div>Christopher Manly</div>
</div>
<div>Coordinator, Library Systems</div>
<div>Cornell University Library Information Technologies</div>
<div>cam2@cornell.edu</div>
<div>607-255-3344</div>
</div>
</div>
</body>
</html>