{"id":2512,"date":"2008-02-13T08:49:41","date_gmt":"2008-02-13T08:49:41","guid":{"rendered":"https:\/\/wordpress.org\/plugins-wp\/events-category\/"},"modified":"2009-08-21T02:47:11","modified_gmt":"2009-08-21T02:47:11","slug":"events-category","status":"closed","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/events-category\/","author":186678,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"0.4","stable_tag":"0.4","tested":"2.6.2","requires":"","requires_php":"","requires_plugins":"","header_name":"Events Category","header_author":"Weston Ruter","header_description":"","assets_banners_color":"","last_updated":"2009-08-21 02:47:11","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"http:\/\/wordpress.org\/extend\/plugins\/events-category\/","header_author_uri":"http:\/\/weston.ruter.net\/","rating":0,"author_block_rating":0,"active_installs":10,"downloads":6428,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description"],"tags":[],"upgrade_notice":[],"ratings":{"1":0,"2":0,"3":0,"4":0,"5":0},"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.4"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[416,1486,166],"plugin_category":[40],"plugin_contributors":[78438],"plugin_business_model":[],"class_list":["post-2512","plugin","type-plugin","status-closed","hentry","plugin_tags-calendar","plugin_tags-events","plugin_tags-posts","plugin_category-calendar-and-events","plugin_contributors-westonruter","plugin_committers-gilzow","plugin_committers-westonruter"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/events-category.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n

Notice: This plugin is not being actively maintained. Other priorities have arisen which have forced development to discontinue. Being open source and free, you are of course free to take the code and improve upon it; if you are a developer and would like to be added as a commiter to this plugin, please contact me<\/a>.<\/em><\/p>\n\n

Seamless event calendar solution which extends the basic WordPress functionality to enable future-dated posts\nto be listed within the blog chronology when they are assigned to a particular post category. The a future-dated post's timestamp\nis used as the time stamp. Upcoming events widget included; includes iCal feed. HTML output contains hCalendar, hCard, geo, and adr\nmicroformats.<\/p>\n\n

Quick Start<\/h4>\n\n
    \n
  1. Activate the plugin<\/li>\n
  2. Create new posts in the \"Events\" category<\/li>\n
  3. Add the Upcoming Events widget to the sidebar<\/li>\n<\/ol>\n\n

    How it works<\/h4>\n\n

    WordPress is designed to serve posts arranged in a chronological order. Because of this\nand because the post is such a fundamental building component of WordPress, it only makes\nsince that an Event Calendar solution for WordPress should take advantage of its core functionality.\nAt the most fundamental level, this plugin enables posts to be used as events by automatically publishing\nany future-dated posts that reside inside of a specific category and its subcategories: this is the \"Events Category\".<\/p>\n\n

    Since events are merely future-dated posts, they may be browsed using WordPress's chronological archives.\nPretty permalinks to these event posts which contain the common year\/month\/day structure are intuatively\nsemantic: the URL to the event itself indicates the event's time. Since WordPress by default displays the future-most\nposts first in a descending-chronological order, the behavior of the index pages under in the events category was changed.\nA new query variable, eventscategory-position<\/code>, is introduced which indicates the current position in the timeline.\nWhen serving the root of a category, this query variable is set to \"0\", which means that the upcoming events will be shown in ascending order.\nIf there are more upcoming events than what is allowed to show per page, then there is a link generated with the usual previous_posts_link()<\/code> (yes,\nthe name is unintuitive, but this is normal for WordPress). The second page of future events\nwould have eventscategory-position<\/code> set to \"1\", and the third page \"2\", and so on.<\/p>\n\n

    If there are events that have already passed, they can be seen by clicking the link generated by next_posts_link()<\/code>.\nUnlike future events which are presented in ascending order, past events are presented in descending order. The first page of past\nevents has eventscategory-position<\/code> set to \"-1\", the second page to \"-2\", and so on. Basically, all that\n eventscategory-position does is it replaces the paged<\/code> paramater, and conceptually it shifts the paged<\/code> paramater.<\/p>\n\n

    As already mentioned, the landing page for the events category lists the next upcoming events, that is, the first page of future results.\nWhen pretty permalinks are enabled, on the second page of future results, the URL would appear as \/category\/events\/future\/2\/<\/code>\n(\/category\/events\/future\/1\/<\/code> and \/category\/events\/future\/<\/code> and \/category\/events\/<\/code> all refer to the same\npage of results where eventscategory-position<\/code> is \"0\"). Likewise, on the first page of past events, the URL would appear as\n \/category\/events\/past\/ (\/category\/events\/past\/1\/<\/code> is equivalent where eventscategory-position<\/code> is \"-1\");\nthe second page of past events would appear as \/category\/events\/past\/2\/<\/code> and so on.<\/p>\n\n

    Note that since all events are posts, the default posts page and feed will filter out all posts dated after the current time;\notherwise all of your future posts will fill the first pages of your results.<\/p>\n\n

    Creating a new event<\/h4>\n\n

    Creating a new event is just creating a new post and assigning it to the \"Events\" category (or a subcategory under it). You may rename this category to something else after\ninitially activiating the plugin. Once you select the \"Events\" category for the post, additional controls will appear asking for the necessary\ninformation to create an event, including the start date-time and end-date time, and the location.<\/p>\n\n

    Upcoming Events Widget<\/h4>\n\n

    Multiple upcoming events widgets may be added to your sidebar(s), and each one may be customized to show only certain categories of events,\nto show a specified number of posts, to include the location, and to customize the date-time format and the address format.\nThe feed links will appear if you are showing only one category.<\/p>\n\n

    Template Tags and Data Formatting<\/h4>\n\n

    The following template tags are introduced:<\/p>\n\n

      \n
    • eventscategory_get_the_time($dt_format = '')<\/code> -- prints the time <\/li>\n
    • eventscategory_the_time($dt_format = '')<\/code> -- echos the preceding function<\/li>\n
    • eventscategory_get_the_location($before = '', $after = '', $adr_format = '')<\/code> -- if no location is provided, nothing is returned<\/li>\n
    • eventscategory_the_location($before = '', $after = '', $adr_format = '')<\/code> -- echos the preceding function<\/li>\n<\/ul>\n\n

      The $dt_format<\/code> (date-time format) is a hybrid version of the format accepted by PHP's date() function.\nFormat characters which are enclosed in brackets are removed (along with other characters) if their presence adds no new information.\nSee the following example date format; the event end date-time is enclosed in curly brackets, in which the first square-bracketted string\nis the separator between the two date-times:<\/p>\n\n

      F jS, [Y @] g[:i][a]{[ - ][F ][j][S, ][Y,] g[:i]a} T\n<\/code><\/pre>\n\n
      The $adr_format<\/code> (address format) is a string incorporating adr microformat class names:<\/p>\n\n
      [%street-address%]\\n[%extended-address%]\\n[%locality%][, %region%][ %postal-code%]\\n[%country-name%]\n<\/code><\/pre>\n\n
      The HTML output from these functions is tagged using hCalendar, hCard, geo, and adr microformats.\nThe default format strings used by these functions can be modified via the Upcoming Events widget configuration,\nor via the main Events Category options page; the formats modified in these sections are independent of each other,\nso you can use a more concise date format in the widget, but have a more verbose format when calling\n    eventscategory_the_time() elsewhere.<\/p>\n\n
      Displaying Event List: Sample category.php Template<\/h4>\n\n
      You can determine if the user is currently seeing future posts if the query variable eventscategory-position<\/code> is less than zero.\nIf it is equal to zero then they are in the present time, meaning the next upcoming events are shown; if it greater than zero, then\nsome page of future events is being viewed. Please locate the file example-templates\/category.php<\/code> in the plugin.<\/p>\n\n
      Displaying an Event: Sample single.php Template<\/h4>\n\n
      The following example includes hCalendar and other microformats if the post being viewed is an event.\nPlease locate the file example-templates\/single.php<\/code> in the plugin.<\/p>\n\n
      Changelog<\/h4>\n\n
      2008-10-10: 0.4<\/em>\n* Large re-write and re-development for WordPress 2.6<\/p>\n\n
      2008-02-13: 0.1 (beta)<\/em><\/p>\n\n
        \n
      • is_events_category()<\/code> now accepts arrays of category IDs or category objects so that is_events_category(get_the_category())<\/code> can be used in the single.php template.<\/li>\n
      • Future events posts now no longer appear on the default posts page nor in the main posts feed.<\/li>\n
      • Event feeds (RSS2 and iCal) are now automatically added to each page.<\/li>\n
      • Event location in iCal feed has been improved<\/li>\n<\/ul>\n\n
        2008-02-12: 0.1 (alpha)<\/em><\/p>\n\n
          \n
        • Initial version released<\/li>\n<\/ul>\n\n
          Todo<\/h4>\n\n
            \n
          1. Seconds should be forbidden in the format, because if the minutes are hidden, the seconds will look like minutes? Or we can only remove the [i] if the [s] is 0<\/li>\n
          2. Tabbing among the events category tabs needs to be resolved (hitting tab from title should go to the start date)<\/li>\n
          3. Javascript validation of data needed, including ensuring that second date and time should maintain diff from first when the first is modified<\/li>\n
          4. ??Category count is broken in Manage Categories page as well as Posts Manage page: Category post count incorrect when in admin managing posts<\/li>\n
          5. Timezones and daylight savings time\n\n
              \n
            1. Setting time at the beginning and end of daylight savings time is buggy.<\/li>\n
            2. Start and end date-time microformats not currently working with daylight savings time<\/li>\n
            3. Should we automatically change gmt_offset when DST starts or ends? We could just do set_option(gmt_offset, date('Z')\/3600) after <\/li>\n
            4. We should always use gmt_post_date - post_date to get the gmt_offset; when saving a post in daylight savings, we'll add\/subtract subtract one from gmt_offset<\/li>\n
            5. Should we be able to specify the timezone that the user is in? with putenv(TZ=) or date_default_timezone_set()<\/li>\n
            6. Verify conversions: from browser form to PHP handler to database to the_time and finally back to the browser form again; verify consistency and validity for timezones and DST<\/li>\n
            7. SOLUTION: Allow user to set the offset each time, and upon save_post, change the gmt_post_date to correspond to the user-defined offset<\/li>\n
            8. save event-gmt-offset in postmeta<\/li>\n
            9. Present a list of all timezones\/offsets for which the user's timezone is automatically selected<\/li>\n
            10. Client-logic determines whether the start or end-date are DST: problem: how will server know when DST? If we have\nthe start time the gmt_date (start - gmt-offset), how do we determine if start time + duration is DST or not DST?<\/li>\n<\/ol><\/li>\n
            11. Add external iCal feeds to display\n\n
                \n
              1. Be able to assign all posts in a feed to a category<\/li>\n
              2. Note that we need to store in postmeta the post-event's source feed and unique identifier<\/li>\n
              3. Do iCal feeds generally keep all feeds from all time? If not, then how do we know when an event was deleted or just stopped from being shown?<\/li>\n
              4. Disable comments for imported feeds?<\/li>\n
              5. Disable editing\/deleting of imported events<\/li>\n
              6. Who should be assigned as the author of these imported posts? By default: admin; but provide drop down to choose<\/li>\n<\/ol><\/li>\n
              7. Add 'category' field to microformat... <\/li>\n
              8. Significant feature:<\/strong> Recurring Events\n\n
                  \n
                1. Once recurring events are supported, we'll have to modify the post-lists in Manage Posts to make them more navigable<\/li>\n<\/ol><\/li>\n
                2. ??Option to filter the_time to include the beginning and end dates, that is, the results from eventscategory_the_time... and include the format specified<\/li>\n
                3. Localize in Japanese<\/li>\n
                4. Significant feature:<\/strong> Event Registration\n\n
                    \n
                  1. Add support for keeping track of attendees; RSVP status may be assigned by registered users via the comments form: http:\/\/microformats.org\/wiki\/hcalendar-brainstorming<\/li>\n
                  2. iCal feed should include this registrant data<\/li>\n<\/ol><\/li>\n<\/ol>","raw_excerpt":"Seamless event calendar solution which extends the basic WordPress functionality to enable future-dated posts\nto be listed within the blog chronology  …","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/2512","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=2512"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/westonruter"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=2512"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=2512"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=2512"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=2512"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=2512"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=2512"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}