andrewbevitt

Unfortunately this means you’re either:

1. not running uWSGI with the built-in PHP interpreter; or
2. are running a very old version of uWSGI.

You also need this: https://github.com/unbit/uwsgi/pull/660

https://uwsgi-docs.readthedocs.org/en/latest/PHP.html#uwsgi-api-support

Here is an example:

cat /etc/uwsgi/apps-available/wordpress-blog.ini
[uwsgi]
uid = www-data
gid = www-data
chown-socket = www-data
plugins = php,cache
php-sapi-name = apache
php-docroot = /srv/www/example.com/public_html
php-allowed-ext = .php
php-index = index.php
php-set = date.timezone=Australia/Sydney
processes = 25
cheaper = 5
cache2 = name=uwsgi_c1,items=1024,blocksize=4096,bitmap=1,purge_lru=1
stats = :7500

and

cat /srv/www/example.com/public_html/wp-config.php | grep UWSGI
define( 'UWSGI_CACHE', 'uwsgi_c1' );
$batcache = array('group'=>UWSGI_CACHE, 'remote'=>1);

I’m sorry but WordPress Object Cache’s must be installed this way. This is not a bug.

The file /home/mywebsite/public_html/wp-content/plugins/uwsgi-object-cache/object-cache.php should not exist – it should have been moved to /home/mywebsite/public_html/wp-content/object-cache.php.

The plugin is not available in Arabic – but could be translated. There are several other translations underway at the moment – if you get in touch at https://andrewbevitt.com/contact/ we can discuss further.

This plugin only provides a WordPress Object Cache. It does not do page caching – for page caching you need to use a plugin which caches pages using the WordPress Object Cache.

Cachify does not use the WordPress Object Cache – so no it won’t work with this plugin.

I use batcache for page caching on top of this plugin.

For define('UWSGI_CACHE', '***'); the *** can be any valid uWSGI cache name – whatever works in your uWSGI config, will work here.

This plugin MUST be installed to the WP_CONTENT_DIR – this is required of all WordPress Object Cache implementations. Is there any reason you can not do this?

+1

Although my solution was

// fixes the plugins_url
 function domain_mapping_plugins_uri( $full_url, $path=NULL, $plugin=NULL ) {
       return str_replace(network_site_url(), trailingslashit( get_site_url() ), $full_url);
 }

The term is parsed by PHP’s strtotime function so you can use anything that is a legitimate value for that function.

If you wanted to show the next month’s worth of events:
[eventlist name=”NAME” starting=”today” until=”+1 month”]

See https://www.php.net/manual/en/function.strtotime.php for more examples.

The events are cached locally based on the setting for external calendars under ‘Calendar Export Settings’ on the plugin settings page. It was placed there because this value originally was meant for caching the external calendars for iCal/RSS exports. In hindsight this is a poor place for this setting so I will move it in the next release.

What you’re experiencing is a result of the Google Calendar feed being accessed in two different ways. The FullCalendar JS pulls down the feed directly and transforms it to display. For the widgets (and iCal/RSS etc) the PHP code pulls down the feed, transforms it, caches it and then sends to the client.

The default cache time is 1 week so if you try changing it to something less you should see changes replicate quicker.

I’ve added an option to the widget to specify the date format. By default it will remain ‘j/M’ but you can change it to whatever you like.

I’ve incorporated this idea into the widget options for the next release.

I think you want this line

https://github.com/andrewbevitt/everycal/blob/master/widgets/title-list.php#L220

Change the format string from ‘j/M’ to ‘F jS Y’ and it should work.

Do you mean below the calendar itself? If so there is the calendar layout template in the plugin settings. You could put the link in there – it will be the same link for all calendars though.

Thanks for your interest!

I’m currently working on some significant changes related to the FullCalendar.js updates and refactoring some of the layout and some other things.

I’m happy to email you a language file to start translating. However there will be a few changes required before the next version is released. You can send me an email from https://andrewbevitt.com/contact/ and I’ll send you the language file.

Portfolio: You can use the “list” view. The shortcode for this displayed in the calendar post editor page. This is simply a list of events within a certain time range so it might not be what you want.

Multiple calendars: Yes definitely possible! Create a second calendar post (Admin Menu -> Events -> Calendars -> Add New) and either: a) link directly to the post page; or b) use the shortcode to embed it in a normal WP page.

Events can appear on any number of calendars.

You can also mark one calendar as a – sort of – global calendar which will include all events marked as “Feature Events”.

Having multiple calendar plugins shouldn’t create these issues unless they use the same custom post type or URI parameter names. Which they probably wouldn’t be but if you wanted to check EveryCal uses types and params starting with ‘ecp1’.

Now onto specific issues:

I’ve only done basic testing on changing the initial date of a repeating event. It works in simple cases however there are plenty of edge cases where it might not work. I expected repeating events would not be changed in this way (mainly because the data shouldn’t need to change). Maybe try changing the date of a one off event – if that works then try to add repeats to that event.

The repeats cache can’t be erased from the WP admin; this is a feature I’m planning to add in the future. You could do it using your database administration tool though: look at the ecp1_repeats table.

I can’t explain why repeats would work on one day but not on another day. Theoretically you should be able to have many repeating events every day of the week. There is an upper bound from the PHP execution time though which would make this impractical for a large number of concurrently repeating events. I have a few ideas though:

a) It might be related to Saturday being the 1st of March. The front end calendar requests all events in the range it needs which somehow might exclude the 1st of March – however this shouldn’t be the case for 2014 where the week starts Monday 24th February.

b) What are you using as the event title, description, etc? Are you using any non-ASCII characters? If you are try removing them as these might cause the event to be dropped if the characters can’t be encoded.