Forum Replies Created
-
Posts
-
Although it doesn’t cover all your feature requests, I did release version 2.0 of the Custom Fields extension that adds a “Hide From Public” checkbox for each custom field. This would address your needs of having some fields that are for admin use only and would be visible to the admin only and also can be used in the reports/exports, but never visible to the public.
This content is restricted to buyers of:
If you want to view this content, you need to buy any product.
If you want to view this content, you need to buy any product.
If you want to view this content, you need to buy any product.
If you want to view this content, you need to buy any product.
This content is restricted to buyers of:
This content is restricted to buyers of:
My plugin has nothing to do with staging mode vs. live mode. That’s completely dependent on how your staging system is set up. Usually when you say “staging” that means a site that is a clone of the live site where you can test things out without it affecting anything on the live site. Then, if everything works on the staging site after all the changes, you push those changes back to the live site to update the database and code on the live site. Again, my plugin has absolutely nothing to do with that. If you are using some plugin to create a “staging” mode, and it doesn’t copy all the database table changes back over to the live site when you switch to “live” mode, then that’s not the fault of my plugin.
The most common form of staging is done via server software that the hosting company provides and has nothing to do with wordpress directly… it simply creates a clone of all your files and your database, and it doesn’t care what software you are running on that site (WordPress, or anything else).The problem remains, where do you specify the empty row, and how do you specify after what entry that row should appear? Again, the custom fields extension adds columns (not rows), and even the Customizer extension only allows you to specify which columns are shown. The plugin has no way of knowing which signups should be shown together with a separator after them.
If it was some kind of fixed setting, such as insert an empty row after every third row, then that could possibly be done. However, you can do that right now with custom CSS that targets your tables. Look up some standard CSS for tables and lists and how to use the ‘nth’ type operator, or the ‘even’ or ‘odd’ operators, to specify how to change the styling for some of the rows (as long as they fall into a repeating pattern such as even, odd, or every ‘nth’ row). I think some custom CSS is probably your best bet right now if there is a pattern to where you want some kind of styling to separate entries. If there is no pattern, however, then it pretty much becomes impossible unless we do some major code changes to somehow allow people to specify which signups belong together as they are signing up.
Thanks for the suggestion. I agree that something like that would be nice. However…
The problem with your suggestion is that custom fields are additional columns in the table displays, and are NOT something that are output in between rows. There is currently no way for you to specify any type of field to appear between rows of volunteers.
This is much more complex than simply allowing a field where you could insert html.
Just in case someone else looks at this thread in the future, after some private emails and the refreshing of my memory on my code, this is not a bug of the current plugin, but rather a feature that doesn’t exist yet and some confusing on how the current email template tags can be used.
As of right now, the email template tags for signup info can only be used for triggers that related to a specific signup, such as when someone signups for a task or clears their signup from a task. In those cases, we have a specific signup we are dealing with, and info from that signup can be used to replace the template tags. Otherwise, if we are doing something like a weekly summary of upcoming events, we can only work with sheet and task template tags as there is currently no “signup loop template” for my code to loop through all the existing signups and display all that info. Something like that would only work within the the task template loop, or possibly the sheet template loop, so that we know which sheet or task to get all the signups for (consider you have 10 different sheets/events in a week, all with many signups).
I’m putting a note to myself for this to be a feature request for a potential future update. This is the newest extension, and has a very small number of users at this point, so I’m open to suggestions for new features to make it more appealing to other users.
Hi Vicki,
Thanks for letting me know. Let me see if I can reproduce the issue and come up with a fix. You are actually only the 3rd person to use this plugin, which was a “subsidized” development deal for a client who need one particular automated email function. I tried to make it more generic to hopefully make it useful for others, and it got super complex very quickly. So, no doubt I missed some things as it’s impossible to test every combination, and I mainly focused on the use case for the individual I developed it for, as well as a few other common cases I could think of.
Anyway, I haven’t had a lot of feedback yet since it’s seems to be working fine for what the other two users use it for. So, thanks for pointing this out. I’ll get to work on it after lunch and hopefully be able to push out an update soon.
I will have to investigate whatever limits I may have put on trigger generation. In order not to slow the site down while the public is using things, I had the code generate the trigger events in a special database ahead of time. If I did not do that, then every time a page would load, my code would have to go through every trigger and test it against every sheet/event in the database, and that would slow things down. Instead, it only has to look to see if there are any triggers set to be run on the current day/time. Obviously, a recurring event like yours with a very large number of dates could make for a very large trigger event database. I’ll have to look at my code again and see how I handled recurring events…. obviously it’s currently not handling them they way you are expecting.
Hi Vicki,
That date is the date the plugin was originally published, not the last update date. It’s still a relatively new extension, but I have updated it twice since its release, and it’s working just fine with the latest versions of WordPress and PHP 8.2.10.
Note that the plugin itself does NOT do the actual sending of emails. Just like the main plugin, this plugin uses the WordPress wp_mail function to actually send the emails. If you are using a plugin that replaces the wp_mail function to connect with a better email SMTP service (highly recommended), then it should still work fine as long as that plugin uses the same parameters and header formats that the wp_mail function uses. I haven’t test specifically with Brevo, but if it’s working fine with the free volunteer sign up sheets plugin, then it should work just fine with this extension.
This content is restricted to buyers of: