davidfcarr

Rob,

The short open tag thing shouldn’t be an issue at this point, if you have the current release installed.

You’re saying you get critical errors when updating the plugin? No other changes? What PHP version?

Re nothing being logged, you might try temporarily enabling DEBUG_LOG_DISPLAY in your wp-config.php. I’ve occasionally seen errors that will be displayed on screen but not written to the log for whatever reason.

I’m not seeing these errors on my test and production servers, so I do need a clue of where to look if the plugin is behaving differently on your website. Could be a conflict with another plugin or something different about the hosting setup.

Anyone still struggling with this: Please try installing RSVPMaker 11.4.2 and let me know if that resolves the issue.

Turns out PHP 8 removed default support for a short tag syntax that I don’t normally use but which occurs in one spot in the rsvpmaker-util.php file.

The reason it took me so long to find the bug: Both my web host and my local dev environment had a php.ini configuration switch turned on that allows short_tags to work in PHP 8.

• This reply was modified 1 month, 3 weeks ago by davidfcarr.

At this point, I’ve gotten so deep into making RSVPMaker work well with the block editor that it would be a substantial project to reenable the classic editor UI. I might do it eventually, just because there are times I’d like to be able to change event settings without going into the editor. But don’t expect that anytime soon.

Sorry for the slow response. Please try version 11.3 and let me know if that resolves the issue.

Thank you!

I just put out a bug fix to address the issue about being able to delete entries from the RSVP Report.

I did try switching a test site to Deutch, but that doesn’t seem to be the issue.

My guess is a conflict with another plugin. Can you use the Inspector in Chrome or Firefox to check whether there are JavaScript errors when the editor screen is loaded for an RSVPMaker event?

If you display the editor sidebar with the document properties, do you see a button labeled RSVP / Event Options? There should be a calendar widget displayed in the sidebar as well.

I’m not sure. Not seeing a similar glitch on any of my own sites or test sites.

Looks like you only have one event active on the website? Is this your first time using RSVPMaker? Did you have any registrations entered for the event as tests? Any other events you created? If you have more than one event, make sure you’re looking at the report for the correct event.

There is some documentation here.

A template is supposed to be an abstract model / outline of the kind of event you typically host, with default content and settings such as whether RSVP collection is active. For example, one of my clients hosts gourmet dinners where the template shows the general organization of the page, but the individual events based on the template have different menus and lists of guest chefs.

When you update a template, you should get a prompt to create/update a series of events based on that template. If you’ve put in a base schedule like First Tuesday at 7 am, it will try to calculate the first Tuesdays of upcoming months and give you a draft post. You can then customize the individual event posts as needed.

Are you still experiencing this issue? With the latest release?

Try updating to version 11.1.2 and let me know if that resolves the issue.

I see the issue and will investigate.

Re: “There isn’t a custom filter to stop the dynamic cache for an admin user, as our plugin does not cache the admin page and logged-in user content; hence, there is no need to add a turn-off custom filter for the dynamic cache.”

Whatever the plugin does differently on the admin pages includes the permissions bug reported here, which is associated with dynamic caching being turned on. Thus, the need for a workaround if I don’t want to have to tell subdomain admins to turn off dynamic caching every time they want to update settings.

Actually, for this to work I can’t network activate the plugin. Instead I use the filter to make it active on the individual subdomain sites outside of the admin pages I don’t want it to mess with. Obviously, a hack, but until they fix this for real …

add_filter( 'option_active_plugins', 'disable_sg_cache_admin' );

function disable_sg_cache_admin( $plugins ) {
if ( strpos($_SERVER['REQUEST_URI'],'wp-admin') && !(strpos($_SERVER['REQUEST_URI'],'index.php') || strpos($_SERVER['REQUEST_URI'],'page=sgo')) ) {
	require (ABSPATH . WPINC . '/pluggable.php');
    // Use the plugin folder and main file name here.
    // is used here as an example
       $plugins_not_needed = array ('sg-cachepress/sg-cachepress.php');
        foreach ( $plugins_not_needed as $plugin ) {
            $key = array_search( $plugin, $plugins );
            if ( false !== $key ) {
                unset( $plugins[ $key ] );
            }
        }
    }
	elseif(!in_array('sg-cachepress/sg-cachepress.php',$plugins))
		$plugins[] = 'sg-cachepress/sg-cachepress.php';

    return $plugins;
}