Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

events() show wrong range start #9

Open
manu37 opened this issue Apr 25, 2018 · 3 comments
Open

events() show wrong range start #9

manu37 opened this issue Apr 25, 2018 · 3 comments
Labels

Comments

@manu37
Copy link

manu37 commented Apr 25, 2018

If I put events(1,2018,12,0); it shows range from nov 2017 to dec 2018. To get it right I have to set events(03,2018,10,0); to get range jan 2018 to dec 2018.

@manu37 manu37 added the bug label Apr 25, 2018
@cmb69
Copy link
Member

cmb69 commented Apr 25, 2018

One issue here is the $past_month == '' check; if you pass 0 as $past_month (which both plugin calls do), the configured default will be used. If the check used the identity operator (===), this issue wouldn't occur. In my opionion it would even be cleaner, if the parameters would default to null, and the function's code would be adapted respectively.

@manu37
Copy link
Author

manu37 commented Apr 26, 2018

ok, there ist a config2.php where $past_month etc. can be modified and therefore do whithout the additional parameters. Its beyound my imagination where config2 can be edited whithin CMSimple_XH.

@cmb69
Copy link
Member

cmb69 commented Apr 26, 2018

I believe config2.php is supposed to contain hidden configuration options, i.e. those that cannot be edited from the plugin administration. If I'm right it should be possible to move options from config2.php to config.php (and vice versa). (It might be sensible to merge both files and to mark the options in metaconfig.php as hidden, or maybe advanced. For my liking, there are already too many config options, though.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants