The banner on our (Drupal 8) town website is a photo image of autumn leaves. I would like to be able to change the banner photo according to the season. Could I use the Rotating Banner module to upload and sequence the photo images? That is, can duration be set in days or weeks instead of minutes or hours? If not via the Rotating Banner module, how else might a seasonal banner change be managed?
I am working with Drupal 8 on Linux and using bash and perl to automate certain steps post-installation to get to a reproducible state for further website development and testing.
I have a weird issue since I moved to a new inernet hosting service : sometimes (but not all the time), when I navigate from an admin page to a normal page of my website, it looks like I'm logged out, but if I refresh the page, I'm logged in again.
I suspect a cache issue, but I didn't change my settings, and I'm not sure to know where to look. Any ideas ?
I am looking for a solution which where user email verification before the admin approval.
As in drupal if we select admin approval required user must be approved by admin first then an email trigger to user which contain the temp. password for first time logged in after then user verify that mail with that then he can logged in
Also what could be options (community and coding) to send notification to admin once user verify the email by customer.
I was having an issue updating the Commerce Core module from 2.25 to 2.27 (security update) via Composer and had to manually update the module via the ZIP file (dumb move, I know).
Now when I run drush pm:security, it's still seeing the old version (2.25).
Is there a command I can run to get this back in sync so that:
1. drush pm:security shows the correct version
2. I can continue to update Commerce Core via Composer (right now, if I attempt to update to 2.28 via Composer, it takes the site down with PHP errors).
The proprietary software upon which Orange County’s previous website had been built represented the best available solution at the time it was developed. Over the course of a decade and a half, as Drupal made quantum evolutionary leaps forward, the county’s proprietary web software proved to be unnecessarily costly and difficult to manage. Upgrades and support for the system were on the decline, and eventually the vendor revealed that the software was slated for end-of-life status.