rerm

Hi mmspires98! Thanks for your question. On all versions, the calendar view requires each day to be clicked into to view notes. However, all notes for each user can be seen on one screen and easily searched within the PRO version of Dynamic Time.

Hi Logan,

The submit button will always be greyed out for future pay periods. This is to prevent users from inadvertently submitting future pay periods before the current one. Admins can always bypass this restriction (and submit future periods) by accessing the timecard from the admin page. Hope this helps!

Hi queenielow,

Thank you for trying out Dynamic Time. The suggestions you provided are much appreciated! They would however, significantly increase the complexity of the plugin. Because most organizations do not have complex pay structures (other than overtime), we don’t have any plans to add more complex pay rates at any time in the future.

Hi mundesigns,
There was a release on 9/5 where part of your request for restrictions was included. An option for “Punch Only” is an additional entry type (under settings) that prevents editing of manual time fields. Not included is restrictions on days, so a user will still be able to add a punch to any day. We hope to expand on this functionality in the near future.

Hi buddhabackpacker,

That is correct, those tables were created by the Dynamic Time plugin on install. To remove the tables, reinstall the plugin. Under settings, look for the last dropdown named “Uninstall Option”. Select “Delete all Plugin Data”. If the plugin is uninstalled with this setting, all tables are dropped.

The option to drop these tables is not a default due to the nature of the data stored. If a user were to accidentally delete the plugin, the organization could lose valuable timecard and accounting data.

Thank you for your understanding!

Hi Otto,

As you have suggested, I downloaded and tested the classic editor plugin. As expected, it’s the traditional interface and the content is unchanged on the admin side.

However, Gutenberg continues to modify the content on the front end, regardless if the classic editor is installed, and regardless if remove_filter(‘the_content’,’wpautop’); is present. Gutenberg is adding <p> and <br> elements inside <style> and <script> tags. Backward compatibility for Gutenberg for turning off wpautop is not even an afterthought, it’s completely lacking.

I appreciate your thoughts but I stand by the one star rating until there is more consideration for backward compatibility.

Hey Otto, I think that’s exactly where the disconnect is…

I’m using remove_filter(‘the_content’,’wpautop’); and Gutenberg does not honor this. So the content is displayed differently the instant Gutenberg is installed, regardless if the post is edited.

Gutenberg is not backward compatible in this way.

Thanks for your reply Otto. There must be some concerns for backward compatibility in the new Gutenberg? If I install Gutenberg now, all past posts and pages where autop was turned off now have <p> littering the code. So, the workaround, as you have suggested is to proactively install the Classic Editor? That’s a low blow to everyone that customized code and depends on future versions of WordPress to maintain some consistency in handling HTML in posts and pages. Customization is what has helped WordPress become so powerful. Having a toggle to disable autop in Gutenberg would certainly smooth the transition.

Hi Jameradam,

If the employee status is set to “Overtime Eligible” through the admin plugin settings, the overtime should calculate automatically for the period. Let me know if this helps, or if I have misunderstood the issue.

Thank you!

Hi jaberadam, You will find this feature in version 3.3. Users that are not admins can access their timecard directly from the WordPress dashboard menu. Thank you!

Hi jaberadam, Sorry I missed this notification. That is a great idea. We will try to include your suggestion in a future release. Thank you!

Hi glgbtf,

Currently all times are recorded in AM/PM format because this format has the best native browser support. Most calculations for this plugin occur in the browser, as do time formats. So in Chrome, you may be able to enter 16:04, and the browser will automatically convert it to 4:04 PM. The full time stamps are stored in the database, so there is no loss of accuracy with the current format.

If we have a chance to address 24 hour format as an option in the future I will certainly do so.

Hi bleford,

Thank you for the insightful suggestion. This seems to be a popular feature request, so I’ve raised the priority in the queue. When we are able to achieve this (possibly by end of summer), I will follow up to let you know.

Hi kh,

By design the payroll user is a WP administrator. This is so payroll can have access to view all time data, and the ability to update the rate, period and payroll settings for all users.

If you would like to describe the structure of your payroll system, please send us a message from https://richardlerma.com/r1cm/. We will try to accommodate any request if possible.

Thank you for the detailed report. We were able to quickly resolve this and release a fix in version 3.1.11.