When creating an exception to a repeat event, when I select (for example) 7 December 2006 and submit this exception. The display which appears in the 'repeat' section of the event create/edit form shows as 7 December 2006.

The exception is correctly created in the database and displays correctly in the monthly calendar view, but for some reason the display on the edit screen is incremented by +1.

This happens consistently, using:

  • Drupal core 4.7.3
  • event.module 1.183.2.8
  • eventrepeat.module 1.39
CommentFileSizeAuthor
#2 exception.jpg30.34 KBgmak

Comments

seanbfuller’s picture

seanbfuller commented

Thanks for the bug report, but I was unable to reproduce your bug. I created a long string of repeating events and added numerous exceptions and they all worked and displayed as intended. I also upgraded to the lastest version of event (1.183.2.8).

Can you try upgrading eventrepeat and testing agian? If it persists, can you provide any additional settings or modules that you are using?

Meanwhile, I'll keep testing for this.

gmak’s picture

gmak commented
StatusFileSize
new exception.jpg30.34 KB

I've upgraded to the latest version (1.43 - cvs - 26/9/06) and the problem persists. Attached is a screenshot of an exception that has just been created for 29 November 2006.

Here's the list of modules that I have activated:

aggregator
amazon
block
blog
blogapi
book
comment
content
event
event_views
eventrepeat
filter
flatforum
forum
freelinking
help
image
image_exact
image_gallery
imagefield
imce
insert_view
lightbox2
menu
node
nodereference
number
optionwidgets
page
panels
porterstemmer
print
profile
search
service_links
simplenews
spamspan
statistics
story
system
tagadelic
taxonomy
taxonomy_context
taxonomy_defaults
teaser_management
text
tinymce
tracker
upload
upload_image
user
userreference
views
views_fusion
views_rss
views_theme_wizard
views_ui
watchdog

Just to be clear, the exception is correct in the calendar but not in the administrative interface (as shown in the screenshot)

seanbfuller’s picture

seanbfuller commented

I was finally able to reproduce this by moving my test site into a timezone with a gmt setting above 0 (gmt +1 or higher). Can you confirm your site's time zone is set in this range?

gmak’s picture

gmak commented

Yes, we are located in London UK, so our timezone is GMT+1.

Glad you were able to reproduce, I was starting to think I was cursed.

seanbfuller’s picture

seanbfuller commented
Version: master » 4.7.x-2.x-dev

Moved to 4.7.x-2.x, but this is probably an issue for HEAD as well.

rmiddle’s picture

rmiddle commented
Status: Active » Fixed

4.7 Branch is being moved to unsupported. If this is still an issue with 5.1 or 5.2 please reopen.

Thanks
Robert

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.