发表文章

[PHP] 备注 #1 Notes #1[whyarewehere]

PhantomWatson 2017-10-9 33

用户

  • 因为管理员创建用户帐户, 所以不需要一个页面, 一般公众可以创建他们自己的帐户
  • /src/Template/Users/account.ctp允许任何人将其角色更改为管理员
  • 我看不到任何管理员添加或编辑用户帐户的方法
  • 说到这里, /src/Template/Users/index.ctp 有一个指向该页的链接 /users/add , 它尚未创建
  • 我看到的字段 Users.end_date 在数据库中, 但没有办法设置在网站上
  • 点击 "嗨!" 来编辑你的帐户信息是不直观的
  • 我不确定新 "雇员" 角色的功能是什么, 与管理员不同。这些要求只需要学生和管理角色, 但如果你的拍摄是能够区分管理员谁监督学生从那些谁不 (例如, 缩小选择领域的可能监督员), 一个 Users.is_supervisor 布尔标志将是方式更简单, 不会使任何角色/授权代码复杂化。
  • /register可供公众访问, 并允许人们为自己创建管理帐户
  • 主页仍然是指创建您自己的帐户
  • /employees 上, 当未指定位置时, 标题行将读取 "当前" 或 "前者"。

验证/授权

  • 我不知道我们是否可以把这些收集到的信息发布给公众 (有些东西, 比如电话号码和紧急联系人应该是隐藏的), 所以现在唯一面向公共的页面应该是一个基本的主页和一个登录页面。
  • 我没有看到一个验证规则 "学生不应该能够创建一个新的工作报告, 如果另一个学生和同一个项目存在没有结束日期"
  • 我看不到验证规则 "学生不应该能够创建一个新的工作报告的开始日期之间的开始和结束日期之间的现有工作报告匹配相同的学生和项目"
  • 为了安全起见, 最好防止加上能够编辑或删除与之无关的记录。我建议这样的授权工作:
    • 管理员-> 一切
    • 学生-> 仅他们自己的工作报告和帐户信息
  • 未登录时仍在页眉中的指向无法访问的站点的链接

工作报告

  • /reports/add中用于指定与工作报告关联的学生的字段被禁用
  • 不提供不指定结束日期的选项, 并且 ReportsTable 中的验证规则要求
  • 我看不出这些要求是在哪里实现的:
    • 查看学生工作
      • 当前 (当前学生的工作与结束日期 > 今天或空)
      • 过去的工作
      • 与特定学生关联
      • 与特定项目关联
  • 当我点击 "按项目名称报告", 我看到 "通知 (8): 试图获取对象的属性 [应用程序/模板 \ 元素 \ 报告 \ 索引. ctp, 85 行]"

项目

  • 并非所有分配给学生的项目都可以归类为社区项目、出版物或网站。事件和未发表的研究, 例如。对项目进行分类并不需要我们的要求, 所以问题可以解决, 完全删除类别的概念, 添加一个捕获所有 "其他项目" 类别, 和/或与学生监督员和收集所有的类别, 他们希望项目的下降。
  • 项目缺少可选的 "基金编号" 字段
  • 似乎没有办法添加项目,指定授予
  • 我看不到满足这一要求的项目的领域: "多行文本字段供资细节 (例如, 5000 美元用于本科生工作, 1万美元用于研究生工作, 等等)"
  • 管理员登录和添加或编辑项目的流程对我来说并不清楚。如果不存在匹配的项目, 则不同项目类型的索引页只显示 "添加" 链接。理想情况下, 有一个 /projects 索引页, 其中带有添加、编辑、删除和查看链接。
  • 字段项目. grant_name 失踪

杂项

  • "继续和 _____, 这样的跛脚占位符消息消失.非常 ableist 的语言
  • 我建议将 "管理员的电子邮件地址" 值添加到 Configure , 以便在一个地方定义, 而不是在多个地方硬您的电子邮件地址。
原文:

Users

  • Since administrators create user accounts, there doesn't need to be a page where the general public can create their own accounts
  • /src/Template/Users/account.ctp lets anyone change their role to an administrator
  • I don't see any means for administrators to add or edit user accounts
  • Speaking of which, /src/Template/Users/index.ctp has a link to the page /users/add, which hasn't been created
  • I see the field Users.end_date in the database, but no means of setting it on the website
  • Clicking on "Hi!" to edit your account information isn't intuitive
  • I'm not sure what the function of the new "employee" role is, as distinct from administrators. The requirements only call for student and admin roles, but if you're shooting for being able to distinguish administrators who supervise students from those who don't (e.g. to narrow down a select field of possible supervisors), a Users.is_supervisor boolean flag would be way simpler and wouldn't complicate any of the role/authorization code.
  • /register is accessible to the public and allows people to create admin accounts for themselves
  • Home page still refers to creating your own account
  • On /employees, when no position is specified, the title line reads "Current ." or "Former ."

Validation / Authorization

  • I'm not sure that it's okay for us to release any of this collected information to the public (and some stuff like phone numbers and emergency contacts should definitely be hidden), so for now the only public-facing pages should be a basic home page and a login page.
  • I don't see a validation rule for "Students should not be able to create a new work report if another one exists for the same student and same project without an end date"
  • I don't see a validation rule for "Students should not be able to create a new work report with a start date that’s between the start and end date of an existing work report matching the same student and project"
  • For safety's sake, it would be good to prevent non-admins from being able to edit or delete records that they're not associated with. I suggest authorization work like this:
    • admins -> everything
    • students -> only their own work reports and account info
  • Links to inaccessible sites still in header when not logged in

Work reports

  • The field in /reports/add for specifying the student associated with a work report is disabled
  • The option to not specify an end date is not provided, and the validation rules in ReportsTable make it required
  • I don't see where these requirements are met:
    • View student work
      • Current (work by current students with end date > today or null)
      • Past work
      • Associated with a specific student
      • Associated with a specific project
  • When I click on "Reports by project name", I see "Notice (8): Trying to get property of non-object [APP/Template\Element\reports\index.ctp, line 85]"

Projects

  • Not all projects assigned to students can be categorized as either community projects, publications, or websites. Events and unpublished research, for instance. Categorizing projects isn't necessary for our requirements, so the problem could be fixed by removing the concept of categories altogether, adding a catch-all "other projects" category, and/or talking to the student supervisors and collecting all of the categories that they expect projects to fall under.
  • Projects are missing an optional "fund number" field
  • It appears that there's no way to add a project and not specify a grant
  • I don't see a field for projects that fulfills this requirement: "Multi-line text field for funding details (e.g. $5k for undergraduate student work, $10k for graduate student work, etc.)"
  • The flow for administrators to log in and add or edit projects isn't clear to me. The index pages for the different project types only display "add" links if no matching projects exist. Ideally, there's a /projects index page with add, edit, delete, view links.
  • The field Projects.grant_name is missing

Miscellaneous

  • "Go ahead and _____ so this lame placeholder message goes away." is very ableist language
  • I recommend adding an "administrator's email address" value to Configure so it's defined in one place instead of hard-coding your email address in multiple places.
相关推荐
最新评论 (23)
ericadeefox 2017-10-9
1

"瘸子" 是我最难打破的 ableist 语言!出收到, 这个名单将在今天有望完成。:)

原文:

Erg, "lame" is my hardest one to break as far as the ableist language goes! Call-out received, this list will be done hopefully by today. :)

ericadeefox 2017-10-9
2

注意: 我已经更改了用户注册是管理员-仅根据这个列表, 但在回顾我认为, 学生应该能够添加自己不需要管理员, 为他们做。这样, 他们就可以马上开始。

原文:

Note: I had changed user registration to be admin-only as per this list, but in retrospect I think students should be able to add themselves without needing an admin to do that for them. That way they can get started right away.

ericadeefox 2017-10-9
3

所以, 现在剩下要做的就是报告索引规范 (由学生、调羹、项目等) 和认证的东西。当然, 我会去通过 finetoothed 梳子的认证的东西。但是, 我想知道: "查看学生工作" 的目标是通过这些不同的内容来排序学生工作, 还是只对显示学生使用这些属性进行工作?到目前为止, 我们的分可以订购学生的项目, 涉及的人, 日期等, 但还不能只显示某些项目。如果目标是仅显示, 请让我知道, 因为我一直想构建搜索功能。

原文:

So, now all that's left to do are the reports indexing specs (view by students, sups, projects, etc) and the auth stuff. Of course I will go through auth stuff with a finetoothed comb. However, I was wondering: is the goal of "View student work" to order student work by these different things, or is it to only show student work with these properties? As of now, our paginator can order student work by their projects, people involved, dates, etc. but cannot yet only show certain projects. If the objective is to only show, let me know because I'd been wanting to build a search feature anyway.

PhantomWatson 2017-10-9
4

筛选, 而不是排序。我建议这些网页:

/reports: 查看所有工作报告
/reports/current: 仅查看当前 (未完成的) 工作报告

$query->where([
    'OR' => [
        function ($exp, $q) {
            return $exp->isNull('end_date');
        },
        function ($exp, $q) {
            return $exp->gte('end_date', date('Y-m-d H:i:s'));
        },
])

/reports/past: 仅查看过去 (已完成) 工作报告

$query->where([
    function ($exp, $q) {
        return $exp->lt('end_date', date('Y-m-d H:i:s'));
    }
])

/reports/student/:student-id: 与特定学生关联
/reports/supervisor/:supervisor-id: 与特定学生关联
/reports/project/:project-id: 与特定项目关联

原文:

Filtering, rather than ordering. I suggest these pages:

/reports: View all work reports
/reports/current: View only current (uncompleted) work reports

$query->where([
    'OR' => [
        function ($exp, $q) {
            return $exp->isNull('end_date');
        },
        function ($exp, $q) {
            return $exp->gte('end_date', date('Y-m-d H:i:s'));
        },
])

/reports/past: View only past (completed) work reports

$query->where([
    function ($exp, $q) {
        return $exp->lt('end_date', date('Y-m-d H:i:s'));
    }
])

/reports/student/:student-id: Associated with a specific student
/reports/supervisor/:supervisor-id: Associated with a specific student
/reports/project/:project-id: Associated with a specific project

ericadeefox 2017-10-9
5

酷, 可以。过滤它是!

原文:

Cool, can do. Filtering it is!

PhantomWatson 2017-10-9
6

我未选中以下内容:

  • "用于指定与工作报告关联的学生的字段/报告/添加" 被禁用..。
    (仍处于禁用状态)
  • 管理员登录和添加或编辑项目的流程对我来说不清楚..。
    (在/项目中, 我看不到任何添加/编辑/删除链接)
  • 我看不到用于满足此要求的项目的字段: "用于融资详细信息的多行文本字段..."
    (我看到 funds.funding_details 已添加, 但 Srikant 建议在 projects 中需要一个字段来记录有关如何在特定项目中分配资金的信息)

我添加了以下内容:

  • /register可供公众查阅..。
  • 主页仍然是指..。
  • 指向无法访问的站点的链接..。
  • /employees 上, 未指定位置时.。
  • 当我点击 "按项目名称报告"..。
  • 字段项目. grant_name 失踪
原文:

I've unchecked the following:

  • "The field in /reports/add for specifying the student associated with a work report is disabled"...
    (It's still disabled)
  • The flow for administrators to log in and add or edit projects isn't clear to me...
    (In /projects, I don't see any add/edit/delete links)
  • I don't see a field for projects that fulfills this requirement: "Multi-line text field for funding details..."
    (I see funds.funding_details was added, but Srikant suggests that we'll need a field in projects to record information about how money is divided up in specific projects)

I've added the following:

  • /register is accessible to the public...
  • Home page still refers to...
  • Links to inaccessible sites...
  • On /employees, when no position is specified...
  • When I click on "Reports by project name"...
  • The field Projects.grant_name is missing
ericadeefox 2017-10-9
7

/register可以向公众开放, 以便学生能够注册自己, 而无需管理员为他们做。我可以添加一些其他的验证措施, 比如向他们的 @bsu 发送一封确认电子邮件。此外, 只有管理员可以添加其他管理员。我可以将 /register 一个管理员的网页完全, 但我觉得这将吃到我们的时间。

中的 "学生" 字段 /reports/add 现在已为 everyone 禁用除管理员。这是让学生只能报告自己的工作。管理员可以在 /reports/add 中为所欲为。这是一个很好的解决办法吗?

/employees 已解决的位置问题。

Reports by name问题已解决。

原文:

/register is accessible to the public in order for students to be able to register themselves without needing an admin to do it for them. I could add some other validation measures, like sending a confirmation email to their @bsu.edu email. Also, only admins can add other admins. I could make /register an admin-only page altogether, but I feel like that's gonna eat into our time.

The student field in /reports/add is now disabled for everyone except admins. This is so that students can only report on their own work. Admins can do whatever they want in /reports/add. Is this a good solution?

Position issue in /employees resolved.

Reports by name issue resolved.

ericadeefox 2017-10-9
8

/projects现在显示管理员的编辑链接。添加链接总是在页眉中可用。我只是试图使项目, 用户, 工作人员等的编辑链接只对管理员可见。

原文:

/projects now shows edit links for admins. Add links are available at the header always. I'm just trying to make the edit links for projects, users, staff etc. visible only to admins.

PhantomWatson 2017-10-9
9

我可以添加一些其他的验证措施, 如发送确认电子邮件

确认电子邮件不是一个坏主意, 但可能没有必要。

此外, 只有管理员可以添加其他管理员。

/register显示一个角色选择器与 "网站管理员" 和 "学生" 作为选项, 虽然出于我不理解的原因, 两个选项实际上都没有被记录在数据库中。role只是被保存为 null , 但这似乎并没有把任何东西搞砸, 因为我找不到任何能明确检查角色 == "学生" 的东西。

原文:

I could add some other validation measures, like sending a confirmation email

Confirmation emails ain't a bad idea, but probably aren't necessary.

Also, only admins can add other admins.

/register shows a role selector with "Site Admin" and "Student" as the options, though for reasons I don't understand, neither option actually gets recorded in the database. role just gets saved as null, but that doesn't seem to screw anything up, as I can't find anything that explicitly checks if the role === 'Student'.

ericadeefox 2017-10-9
10

呦.Welp, 我明天就要大修了 /register

原文:

Whoops. Welp, I will be overhauling /register tomorrow then.

PhantomWatson 2017-10-9
11

我可以做/注册一个只管理页面

是的, 就是这个意思。至少在项目要求改变之前。

"学生" 域/报告/添加现在已为除管理员之外的所有人禁用

提示:此行具有忽略输入的内容并始终使 student_id 成为用户 id 的效果。

这是一个很好的解决办法吗?

是的!我想不出一个非需要向别人报告工作的用例。

旁: 我刚注意到一个新问题。

  • 因为 id 是注册表单中的字段, 所以如果您输入其他人的 ID, 它将有效地使其成为编辑窗体。当我试图使一个新的学生帐户与相同的假冒北京 ID 作为一个现有的管理帐户, 它实际上覆盖的管理帐户。
  • 如果网站使用得当, 我不认为这是一个问题, 但一个错误的学生 ID 可能会导致混乱。
  • 如果我们要防止这种情况发生, 最简单的解决方案是使 Users.id 一个简单的自动键并添加 Users.bsu_id 来跟踪这些数据。
原文:

I could make /register an admin-only page

Yep, that's the idea. At least until the project requirements change.

The student field in /reports/add is now disabled for everyone except admins

Heads-up: This line has the effect of ignoring what was entered and always making student_id the ID of the user.

Is this a good solution?

Yep! I can't think of a use case where a non-admin would need to report work for someone else.

Sidenote: I just noticed a new issue.

  • Because id is a field in the registration form, it effectively makes it an edit form if you enter someone else's ID. When I tried to make a new student account with the same fake BSU ID as an existing admin account, it actually overwrote the admin account.
  • If the site's being used properly, I wouldn't expect this to be an issue, but a mistyped student ID might cause chaos.
  • If we'd like to prevent this, the simplest solution would be making Users.id a simple auto-incremented key and adding Users.bsu_id to keep track of this data.
ericadeefox 2017-10-9
12
  • 因为 id 是注册表单中的字段, 所以如果您输入其他人的 ID, 它将有效地使其成为编辑窗体。当我试图使一个新的学生帐户与相同的假冒北京 ID 作为一个现有的管理帐户, 它实际上覆盖的管理帐户。

我的解决方案:

 $oldUser = $this->Users->find()
    ->where(['id' => $user->id])
    ->first();
if (isset($oldUser->id)) {
    return $this->Flash->error('This user ID is already in use?');
}
原文:
  • Because id is a field in the registration form, it effectively makes it an edit form if you enter someone else's ID. When I tried to make a new student account with the same fake BSU ID as an existing admin account, it actually overwrote the admin account.

My solution:

 $oldUser = $this->Users->find()
    ->where(['id' => $user->id])
    ->first();
if (isset($oldUser->id)) {
    return $this->Flash->error('This user ID is already in use?');
}
PhantomWatson 2017-10-9
13

好!但是如果你想提高效率, 你可以..。

if (!$user->isNew()) {
    return $this->Flash->error('This user ID is already in use?');
}
原文:

Nice! But if you want to be extra efficient, you could just...

if (!$user->isNew()) {
    return $this->Flash->error('This user ID is already in use?');
}
ericadeefox 2017-10-9
14

oml 我能做到吗?真?现在这样做。然后, 整个 users 节应该完成。

我主要关心的是使 /register 管理员只会吸收管理员的时间 (阅读: 我的时间, 您的时间, Srikant 的时间等) 添加用户。不过我不介意做大部分的事情

原文:

oml I can do that? Really? Doing that now. Then the whole users section should be done.

My main concern with making /register admin-only was that it would suck up admins' time (read: my time, your time, Srikant's time, etc) adding users. I don't mind doing the bulk of this, though.

ericadeefox 2017-10-9
15
  • 我看不到用于满足此要求的项目的字段: "用于融资详细信息的多行文本字段..."
    (我看到 funds.funding_details 已添加, 但 Srikant 建议在 projects 中需要一个字段来记录有关如何在特定项目中分配资金的信息)

我担心在项目页面中放置任何资金细节。管理员可以参考基金号, 并在该基金的页面中查看详细信息, 但如果我们在项目部分得到了资金细节, 那么它就不再是管理员的了。

原文:
  • I don't see a field for projects that fulfills this requirement: "Multi-line text field for funding details..."
    (I see funds.funding_details was added, but Srikant suggests that we'll need a field in projects to record information about how money is divided up in specific projects)

I'm apprehensive about putting any funding details in project pages. Admins can reference the fund number, and see details in the page for the fund, but if we've got funding details in the project section then it's no longer admin-only.

PhantomWatson 2017-10-9
16

我担心在项目页面中放置任何资金细节。管理员可以参考基金编号, 并查看基金页面中的详细信息

您的意思是让 /projects/view/:id 排除 Projects.fund_details , 而不是在 /funds/view/:id 上显示该字段, 就像在与给定基金关联的所有项目的详细信息列表中一样?

如果我们已经得到了项目部分的资金细节, 那么它就不再是管理员的了。

为什么在添加 fund_details 字段之后才添加/编辑项目是管理员的?

原文:

I'm apprehensive about putting any funding details in project pages. Admins can reference the fund number, and see details in the page for the fund

Do you mean having /projects/view/:id exclude Projects.fund_details and instead having that field visible on /funds/view/:id, like in a list of details for all projects associated with a given fund?

if we've got funding details in the project section then it's no longer admin-only.

Why won't project adding/editing be admin-only after we add the fund_details field?

ericadeefox 2017-10-9
17

我担心在项目页面中放置任何资金细节。管理员可以参考基金编号, 并查看基金页面中的详细信息

您的意思是让 /projects/view/:id 排除 Projects.fund_details , 而不是在 /funds/view/:id 上显示该字段, 就像在与给定基金关联的所有项目的详细信息列表中一样?

没错!

如果我们已经得到了项目部分的资金细节, 那么它就不再是管理员的了。

为什么在添加 fund_details 字段之后才添加/编辑项目是管理员的?

学生可以添加 & 编辑 (他们自己的) 项目。但我现在已经设置好了, 所有的资金都是管理的。学生只能看到基金号;不过, 我想设置它, 以便管理员可以点击项目页面上的基金号码, 并看到资金的细节。学生是否应该获得这些信息?

原文:

I'm apprehensive about putting any funding details in project pages. Admins can reference the fund number, and see details in the page for the fund

Do you mean having /projects/view/:id exclude Projects.fund_details and instead having that field visible on /funds/view/:id, like in a list of details for all projects associated with a given fund?

Yep, exactly!

if we've got funding details in the project section then it's no longer admin-only.

Why won't project adding/editing be admin-only after we add the fund_details field?

Students can add & edit (their own) projects. But I have it set up now so that everything to do with funding is admin-only. Students can only see fund numbers; however, I'd like to set it up so that admins can click on the fund numbers in the project pages and see the funding details. Should students have access to this information?

ericadeefox 2017-10-9
18

如果存在针对同一学生 & 项目的报告, 并且 end_date 为 null 或在今天或将来, 学生将无法创建报告。基本上他们不能创建重复的工作报告。

原文:

Students now cannot create reports if a report exists for the same student & project and end_date is null or today or in the future. Basically they can't create duplicate work reports.

PhantomWatson 2017-10-9
19

没错!

我会做两个, 只是为了节省人们不得不点击到第二页, 以获取项目的其余信息。在上具有来自其他模型的所有关联数据 /funds/view/:id , 但将项目记录中的所有字段都显示在上 /projects/view/:id

学生可以添加 & 编辑 (他们自己的) 项目。

Whuh 哦我们的需求要求项目添加/编辑为仅管理员。

学生是否应该获得这些信息?

我们的要求说, 学生应该只能够添加和编辑自己的工作报告和用户信息。学生需要与之交互的其他模型中的唯一信息是 <select> 在工作报表窗体中填充现有项目/主管的字段。

原文:

Yep, exactly!

I'd do both, just to save people from having to click over to a second page to get the rest of the info for a project. Have all associated data from other models on /funds/view/:id, but also have all fields from a project record visible on /projects/view/:id.

Students can add & edit (their own) projects.

Whuh oh. Our requirements call for project adding/editing to be admin-only.

Should students have access to this information?

Our requirements say that students should only be able to add and edit their own work reports and user info. The only information from other models that students need to interact with are <select> fields populated with existing projects/supervisors in work report forms.

ericadeefox 2017-10-9
20

我会做两个, 只是为了节省人们不得不点击到第二页, 以获取项目的其余信息。在上具有来自其他模型的所有关联数据 /funds/view/:id , 但将项目记录中的所有字段都显示在上 /projects/view/:id

嗯.除了在数据库中拥有一个全新的字段之外, 我还可以运行一个查询来查找该特定基金的 funding_details , 并在弹出中显示详细信息。

Whuh 哦我们的需求要求项目添加/编辑为仅管理员。

呦.我会修好的问题: 学生是否应该能够查看项目?

原文:

I'd do both, just to save people from having to click over to a second page to get the rest of the info for a project. Have all associated data from other models on /funds/view/:id, but also have all fields from a project record visible on /projects/view/:id.

Hmm... instead of having a whole new field in the database, I could just run a query that finds the funding_details for that particular fund and displays the details in a popover?

Whuh oh. Our requirements call for project adding/editing to be admin-only.

Whoops. I'll fix that. Question: should students be able to view projects?

PhantomWatson 2017-10-9
21

嗯.而不是在数据库中有一个全新的字段, 我可以只运行一个查询, 找到该特定基金的 funding_details, 并显示在一个弹出的细节?

不, 我向您发送的数据库结构是以tooootally的方式设置的。共享相同 Projects.fund_number 的多个项目可能具有不同 Project.fund_details 。喜欢这个:

Project 1 (The Culling)
Fund: 8675309 (General budget)
Details: $2,000 for rare African parrots, $30 for one hammer

Project 2 (The Cleanup)
Fund: 8675309 (General budget)
Details: $20 for a mop, $5 for bleach, $80 for empty pillows to put the feathers in

学生是否应该能够查看项目?

没有特别的理由让学生查看项目名称以外的任何东西, 所以我不会费心设置学生访问项目的资金信息。

原文:

Hmm... instead of having a whole new field in the database, I could just run a query that finds the funding_details for that particular fund and displays the details in a popover?

Nope, the database structure that I sent you was set up that way tooootally on purpose. Multiple projects that share the same Projects.fund_number can have different Project.fund_details. Like this:

Project 1 (The Culling)
Fund: 8675309 (General budget)
Details: $2,000 for rare African parrots, $30 for one hammer

Project 2 (The Cleanup)
Fund: 8675309 (General budget)
Details: $20 for a mop, $5 for bleach, $80 for empty pillows to put the feathers in

should students be able to view projects?

There's no particular reason for students to view anything other than project names, so I wouldn't bother setting up student access to project funding info.

ericadeefox 2017-10-9
22

酷, 我添加了 Projects.funding_details 和限制学生只查看 & 索引项目。包括删除指向引用添加 & 编辑项目的链接 (如果一个是学生)。

原文:

Cool, I added Projects.funding_details and restricted students to just viewing & indexing Projects. Including removing links to reference adding & editing Projects, if one is a student.

ericadeefox 2017-10-9
23

Projects.grant_name已添加到 sql 中, 在窗体中创建的字段和测试扩展为包括 grant_name 。现在我已经关闭了这个问题, 但如果我再次查看列表, 并看到其中的任何一个没有实现或不达标, 我将重新开始。

原文:

Projects.grant_name has been added in sql, field created in form, and testing expanded to include grant_name. For now I have closed the issue but I'll reopen if if I go through the list again and see that any of it is not implemented or sub-par.

返回
发表文章
PhantomWatson
文章数
1
评论数
8
注册排名
60843