Volunteer sign ups displayed list

Same question was asked yesterday:
https://www.ads-software.com/support/topic/css-to-group-tasks-by-day/

Sorry, but with adding the task description, along with the new Custom Fields extension, and the overall re-working of the code, it was better to separate each task out to its own table (they are still arranged by date) and put some of that info in the heading above each table, otherwise there were simply too many columns to try to fit into one table on most screens. When all the tasks were in one table, you would have a lot of empty columns — for example if you had quantities and item details for one task, but not for any of the others, those columns still had to be there for all tasks.

For now, it’s just that one view, unless you use the Calendar extension. If enough people request the single table view I can think about adding it back in as a future option or addon. In the meantime, if you liked the old way, you can download the previous version (before 3) and use that, as it will still work just fine.

Throwing two cents in here (maybe this isn’t the place?). I get why it is the way it is now. I also don’t love it from an ease-of-use perspective, but do like that it fits better column-wise. I wonder if there were different formatting, or formatting options for those that can’t/don’t want to edit CSS, that would make the date and task title stand out better. I personally would have swapped the order of the task and the date; put date FIRST, then task 2nd. Date set as a heading (similar formatting as it was in the old version, and then the task name set in bold. Right now, having none of it formatted as anything other than text makes it harder for the date and task name to stand out.

I have it on my to-do list to go into all my client sites and manually edit the CSS to do this, but figured I’d throw it out here. I think swapping the date/task and adding formatting might mitigate some of the resistance to the new separate table format. Just a thought.

One other note — to your suggestion of possibly adding the single-table back as an option. I would like that, particularly if it were on a sheet-by-sheet basis, rather than global all-or-nothing.

Thanks for the additional comments. I always appreciate ideas, although it’s impossible to make everyone happy without a huge bloated code base and thousands of confusing options.

You are correct in that this probably isn’t the place, so we can move it to my feature requests forum, or private email, to discuss further if needed.

People who purchase extensions, donate, or leave good reviews, get a bit of a higher priority! =)

So far, the well over 100 hours I put into this update, and the new Custom Fields extension, as well as updating all the other extensions, has not paid off at all (only a couple additional sales). So I’m hesitant to put a lot more time into this plugin, which I haven’t even used myself since my son was in grade school 7 years ago. I will probably keep working at it whenever I’m not overloaded with custom programming projects, because it is a type of “puzzle” that I enjoy, and I’d still like to make a much better calendar integration (looking at the FullCalendar javascript calendar now), with real repeating events (which means a huge database structure rewrite). That may end up having to be an all new “pro” version with some initial functions to import from this free version… but, that’s still a long ways off as it’s easily a couple hundred hours more work.

In the meantime, one of my ideas that might fit the needs of the 2 people (out of over 2000 active installs) that like the old single table display better, would be to somehow integrate the dataTables jQuery plugin into display on the front end as well (since it’s all loaded up for Admin now), and offer one giant table view using dataTables, so columns can be hidden as needed, and sorted/searched (for those who have a LOT of tasks for a sheet). Another possibility to maybe generate some revenue to keep this going would be to add that kind of option into the super cheap Customizer (still less than $10) extension.

I know that an extremely small percentage of WordPress users will ever pay for any extensions, as there is the whole “free” mentality of the WordPress community. But, at the same time, if I keep putting more and more into the free version, the time I spend on coding and answering all the support questions doesn’t get compensated at all, and don’t give me a lot of incentive to keep doing this.

Please do feel free to move this to feature requests – haven’t seen much activity on that thread so wasn’t sure if anyone was still looking there. I’ll post there regarding my views on a Pro version! ??
Kym

Thanks.

I’m actually working on putting alternate layout options into the Customizer, to encourage more people to support development with that under $10 extension. Keeping the price the same for now, even though I’ve added a lot of new features to it… hoping that the non-profits and others that use this plugin can at least afford $10 to help keep this going. I’m going to put the consolidated table option, as well as a datatables option, in there. That way I don’t add extra bloat to the main plugin if people don’t care for those other options. Will need a couple of minor modifications to this main plugin to allow replacing the new default views.

When I install the plugin, only half of the text is translated into my locale (danish). I would like to contribute, but at https://translate.www.ads-software.com/projects/wp-plugins/pta-volunteer-sign-up-sheets/ i get the message:

“This plugin is not properly prepared for localization (View detailed logs on Slack). If you would like to translate this plugin, please contact the author.”

Is there a way to contribute to the translation of the rest of the items.

• This reply was modified 4 years, 10 months ago by tomoddershede.
• This reply was modified 4 years, 10 months ago by tomoddershede.

Yes… any help with updating the translations would be great! Many of them are quite old, so they don’t have many of the new text added over several years of updates, and especially this last big update.

All the files needed are in the languages folder of my plugin. The main template is the .pot file which you could probably use to update the Danish translation. Most people do translations with that and something like PoEdit.

The reason you see that message here is that the “text domain” of my plugin does NOT match the main folder and main file name exactly. I already had released the plugin for several years, with several translations, before WordPress started offering the online translation tools with the new text domain requirements. Too late for me to redo all the text domains in my plugin without breaking all the existing translations.

Once you have the translation update, just send me the .po and .mo files, and I’ll include them in the next update. Contact me privately for that, please.

Thanks!

Thank you… Will do