I've setup a Drupal 8 on this Docker image. Everything works perfectly except one thing: images.
Let me explain: I created a content type with an image field. When I create a node of this content type, I can upload an image, everything works well. However I can't create a second one. I have an error and this entry in the logs
The upload directory public://2017-09 for the file field field_poster could not be created or is not accessible. A newly uploaded file could not be saved in this directory as a consequence, and the upload was canceled.
My guess is a permission issue, but, even a chmod -R 777 does not help. Can anybody help? Many thanks :)submitted by /u/Axiol
Future-proof your website, speed its delivery and promote consistency by building with Atomic Design principles. Modern websites assume more business responsibility and importance than ever before. As a result, they’ve grown into immensely complex organisms. With their greater size, you now need formal systems to make large websites manageable again - which is why today’s top digital organizations are turning to Atomic design.Language Undefined
Valuebound: How to secure your user’s private data from unauthorised access by enabling SSL on your web server
As a member of development team, I used to develop web applications using Drupal CMS without worrying about HTTP or HTTPS as it has to be added by dev operational team in my organization. On the serious note “How the Secure Sockets Layer (SSL) prepended to the existing URL” and How does it make a huge difference? Why it is important to make your web URL prepend https instead of HTTP.
Today SSL has become an eye-glazing topic and people want to know more about it so that they can protect their data from unauthorized access. In this blog post, we will take a brief look at basics of SSL and discuss how to secure the website running on Apache with HTTPS. Don’t worry! It's not a rocket science and very simple to secure your site as well as private data. In between, we will also…
Hello, Drupal friends!
Our team want to make it big at DrupalCon. We prepared the session and two BoFs for you.A LEADER OR A MANAGER? HOW TO DEFINE YOUR LEADERSHIP STAND
Our Head of Organizational development wil tell you how to define a leadership stand of yours. Knowing what you stand for in this life helps to get on your own feet and achieve outstanding results both in professional area and in self-realization.DRUPAL FOR A HIGHER EDUCATION
Our senior developer initiates the discussion on Drupal solutions for a higher education and science. The aim of this BoF is to gather Drupal experts and higher education representatives: that would allow us all to hear about the problems and the possible solutions from the first-person point of view.MARKETING CHALLENGES IN THE DRUPAL WORLD
Another BoF is aimed at disclosing challenges we face while promoting and selling Drupal services, building the company image and communicating with a target audience. If we know the problems - we can find the solutions.
Drop a visit!
Everybody seems to build SPAs now. Single-page applications are a big deal: they provide good UX, speed; provide the full control over the markup in Drupal.
We played with Vue.js a bit, and created a simple SPA application. You can use Drupal on the back-end: you’ll find the necessary instructions inside of the article.
I'm having some issues on various D7 sites with some cache tables growing stupidly large (e.g cache_metadata or cache_menu) which then makes drush cc all very slow.
Do you think that there is any problem if I setup a nightly linux cronjob which will be truncating cache and cache_* tables apart from cache_form? And after that I plan on executing a drush cc all for safety.
p.s I do not plan on investigating and trying to fix the root cause that makes those tables grow large.submitted by /u/cherouvim