Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
I successfully got Drupal 8 installed on my Ubuntu 16.04 LTS machine, however I cannot access any other page other than the index / home (http://webserver/) page. When I try to manage the site (eg. http://webserver/admin/structure) I get a 404 error page like this:
Not Found
The requested URL /admin/structure was not found on this server.
Apache/2.4.18 (Ubuntu) Server at webserver Port 80
In the "Best Practice Site Architecture in Drupal 8" video by Pantheon , one of the guys says that the use of taxonomy is more of a Drupal 6 design pattern, and that they barely use it anymore. Watch the video staring from here to hear for yourself what he says about this.
Which design patterns are recommended for Drupal 8 projects, that replaces the need for taxonomies?
eMart eCommerce theme is a creative multi-purpose responsive Drupal 8 theme with Drupal commerce features. It is well suited for e-commerce business websites and non e-commerce websites. eMart eCommerce theme is very flexible, easily customizable and well documented.
eMart eCommerce theme is the first Drupal 8 e-commerce theme from Zymphonies team. We have worked on many e-commerce customers projects. We do any kind of Drupal e-commerce end to end design and development.
When I went to clear my cache on my Drupal 8.5.3 site using Drush, I got the above-referenced error message. I was able to clear the cache through the menu system, but this slows me down.
After doing some research, it appears that this is a symphony problem with a simple solution of changing the yaml files to UTF-8. So, I went into Notepad++ and opened my *.info.yml and *.libraries.yml to see if they were encoded in a different format. Nope, they were both UTF-8.
Has anyone else encountered this error and/or can someone lead me in the right direction?
When editing an added node, I can't figure out how to ensure the taxonomy field within my custom plugin populates with what was previously selected, using the "default_value."
A second problem is that, when viewing the node, it shows the taxonomy term id -- not the term itself.