I'm using SmartDate along with fullcalendar 4.0.0_RC1. I have run into this particular problem and I can't seem to figure out how to address this. I have set up an events content type, created a few events and have created a view using the events type and the fullcalendar. I need the month view and the list view, however, on the month view in the calendar grid, time is displayed as 6: 30p. I want to change this to display 6: 30pm. How can I go about it? I can't seem to find this anywhere in the settings.
I have switched my admin themes to Claro from Adminimal recently and never noticed the new admin toolbar of Claro. Older sites still appear in the Adminimal toolbar style, while a fresh Drupal install shows another one, which i like to have.
I have uninstalled the Admin Toolbar module which i believed made the design of the toolbar, but it looks the same … i cannot figure out how to set this up. Both sites are in Drupal 11.4.1, and so Claro is.
Some time ago I reported a PostgreSQL injection vulnerability in Drupal. It appeared to have been repaired for a while, but since 11.3.13 it seems to have been somehow 're-introduced', because Patchman, used by my hosting provider reports to have repaired that vulnerability again with the latest updates.
Dirk Engelage
To the house of a friend the road is never long ...
I've been thinking about the 3rd party libraries folder (generally located at [WEBROOT/libraries]. I have the permissions for this directory set at 755, as I do with other directories in Drupal. But when I think about it, this could be a security risk, as these are 3rd party libraries, and could be an opening for exploits. I also don't see any reason any of these directories should be writing files. But, I'm also not really a server guy.
Recently I received a message from my hosting provider regarding a vulnerability in two websites running Drupal 11.3.10:
The vulnerability (a code-injection) has been found in the database-environment of your Drupal install, in the file: condition.php.
That was patched by patchman they run automatically. It appears to be a vulnerability still present in the latest version of Drupal. Because after creating a fresh 11.3.10 install on a subdomain, I receive the exact same alert.
That's why I post this here, so it can be taken up and fixed ASAP.