Laravel: prevent user from accessing past and future events -


i have laravel application events, of happened in past, of them current , organised in future. table 'events' looks follows:

+----+-------------+------------+-------------------+---------------------+---------------------------+---------------------+---------------------+ | id | category_id | event_name | event_description | event_startdate     | event_closedate           | created_at          | updated_at          | +----+-------------+------------+-------------------+---------------------+---------------------------+---------------------+---------------------+ |  1 |           1 | event 1    | event 1           | 2016-05-02 00:00:00 | 2016-06-30 00:00:00       | 2016-07-07 15:59:03 | 2016-07-08 12:26:07 | |  2 |           1 | event 2    | event 2           | 2016-06-02 00:00:00 | 2016-07-30 00:00:00       | 2016-07-07 15:59:03 | 2016-07-08 12:26:22 | |  3 |           2 | event 3    | event 3           | 2016-07-02 00:00:00 | 2016-08-19 00:00:00       | 2016-07-07 15:59:03 | 2016-07-08 12:27:04 | |  4 |           2 | event 4    | event 4           | 2016-09-01 00:00:00 | 2016-10-30 00:00:00       | 2016-07-07 15:59:03 | 2016-07-07 15:59:03 | +----+-------------+------------+-------------------+---------------------+---------------------------+---------------------+---------------------+

and each event contains number of items table follows:

+----+------------+-----------+-----------------------+ | id | event_id   | item_name | item_description      | +----+------------+-----------+-----------------------+ |  1 |          1 | item 1    | item 1 - description  | |  2 |          1 | item 2    | item 2 - description  | |  3 |          2 | item 3    | item 3 - description  | |  4 |          2 | item 4    | item 4 - description  | |  5 |          3 | item 5    | item 5 - description  |

i'm displaying current events on homepage. in example, event 2 , 3 current events. each event has link user view items belonging event. 

http://localhost:5000/event/2/items http://localhost:5000/event/3/items

i prevent user able view non-current events (e.g. events past , in future). in example, means 'not found' page (or similar) should shown if user tries go to:

 http://localhost:5000/event/1/items  http://localhost:5000/event/4/items

how can prevented?

you can use findorfail() method additional clause.

public function show($eventid) {     $now = carbon::now();     $event = event::where('event_startdate', '<=', $now)         ->where('event_closedate', '>=', $now)         ->findorfail($eventid);      //returning specific view }

Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more