Drupal News

agoradesign: Using add to cart links instead of forms in Drupal Commerce 2

Main Drupal Feed - Sat, 03/03/2018 - 19:13
Today I'm introducing you to a new contrib module, I've created for allowing "add to cart" (or wishlist) buttons as links instead of forms. This helps to circumvent some unfortunate Drupal core limitations, when you want to build overview pages or blocks.

hi i Wactvh dsfsdfsdf

Drupal News Org - Sat, 03/03/2018 - 18:21

hi i Wactvh dsfsdfsdfhi i Wactvh dsfsdfsdfhi i Wactvh dsfsdfsdfhi i Wactvh dsfsdfsdf

Qatar Zymphonies Theme

Drupal Themes - Sat, 03/03/2018 - 17:58

Qatar Zymphonies Theme is a free mobile-first Bootstrap 4 theme. It has many useful features. It has latest Bootstrap and Font Awesome framework. Qatar Zymphonies Theme is completely free and it can be used by world wide Drupal users.

Live Demo Advanced Themes

Follow us in Twitter & Like us on Facebook to get free/premium theme updates, Drupal tips, tricks & news

Theme designed by FreeBiezz.com & developed by Zymphonies.com

Features

  • Bootstrap v4
  • Font Awesome v5
  • Mobile-first theme
  • Custom menu bar
  • Sticky header
  • In-build slider
  • Light weight theme
  • Fully responsive design
  • More informations in header
    • Quick contact details
    • Social media links
  • Included Sass & Compass source file
    • Colors are stored in Sass variable
    • Well organized Sass code
  • Custom slider - Unlimited image upload
Slider/Banner Configuration

Slider can configure completely from theme settings page. It has control to specify no of required slides, upload image, add title and description etc.

Connect with Zymphonies Contact Zymphonies

Have Queries? Click here to contact Zymphonies

  • Free theme customization & additional features
  • Drupal custom theme development
  • Drupal website design & development
  • Drupal website migration

Sponsored by Zymphonies

Live!!Stream~ Deontay Wilder vs Luis Ortiz Live Boxing Online TV

Drupal News Org - Sat, 03/03/2018 - 17:51

Live!! Deontay Wilder vs Luis Ortiz Live Boxing Online TV

Hello Viewers. Welcome to Watch wilder vs ortiz Live Stream Boxing Match Online. Enjoy wilder vs ortiz Live online PBC Boxing Free on PC, Laptop, IOS, ANDROID, MAC, Windows, ROKU. and All other devices. Enjoy wilder vs ortiz Live Stream Tonight at 9 pm ET on Showtime, Deontay Wilder returns to action to defend his WBC heavyweight title against Luis Ortiz in the main event of a doubleheader from Brooklyn. Wil Esco will be here to cover the round-by-round for both of tonight's bouts. Online Tv Coverage. Just Follow The Links Bellow.

WATCH LIVE :  Wilder vs Ortiz FIGHT LIVE  WATCH LIVE : CLICK HERE TO WATCH LIVE

Wilder vs. Ortiz Weigh-In Stream - BROOKLYN - Unbeaten WBC Heavyweight World Champion Deontay Wilder and unbeaten contender Luis Ortiz exchanged words and went face to face How to stream Deontay Wilder vs. Luis Ortiz live online in the USA, UK, Canada, Australia, or elsewhere around the globe. Undefeated heavyweight champion Deontay Wilder is set to face Luis Ortiz at the Barclays Center on Saturday March 3rd, 2018. The WBC heavyweight title will be on the line. Deontay Wilder vs Luis Ortiz Live Boxing Online TV. Deontay Wilder vs Luis Ortiz Live Boxing Online TV Deontay Wilder vs Luis Ortiz Live Boxing Online TV

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

;

Showtime!.Deontay Wilder vs Luis Ortiz Live Fight Free Deontay Wilder vs. Luis Ortiz: Fight Time, Date, Live Stream and TV 

Drupal version: Drupal 4.5.x or older

(Watch/Live)..Wilder vs Ortiz Fight Live Stream Free Showtime Boxing

Drupal News Org - Sat, 03/03/2018 - 16:37

(Watch/Live)..Wilder vs Ortiz Fight Live Stream Free Showtime Boxing.....(Watch/Live)..Wilder vs Ortiz Fight Live Stream Free Showtime Boxing....(Watch/Live)..Wilder vs Ortiz Fight Live Stream Free Showtime Boxing

Drupal version: Drupal 4.5.x or older

Ashday's Digital Ecosystem and Development Tips: Drupal Search: Solr vs Search Module

Main Drupal Feed - Fri, 03/02/2018 - 22:09

Drupal isn’t known as a particularly lightweight content management system and that is one of the reasons we love it, right? It is meant to handle large amounts of complex content. A problem occurs when you have a site that is just flush with content of different types, how do you get users to it? Navigation can only get you so far sometimes. We have personally seen this on everything from large-scale publishing sites to medical practice sites.

Jeff Potts: Quick look at Acquia Reservoir, a Headless Drupal Distribution

Main Drupal Feed - Fri, 03/02/2018 - 21:00

Drupal is a very popular open source Web Content Management system. One of its key characteristics is that it owns both the back-end repository where content is stored and the front-end where content is rendered. In CMS parlance this is typically called a “coupled” CMS because the front-end and the back-end are coupled together.

Historically, the coupled nature of Drupal was a benefit most of the time because it facilitated a fast time-to-market. In many cases, customers could just install Drupal, define their content types, install or develop a theme, and they had a web site up-and-running that made it easy for non-technical content editors to manage the content of that web site.

But as architectural styles have shifted to “API-first” and Single Page Applications (SPAs) written in client-side frameworks like Angular and React and with many clients finding themselves distributing content to multiple channels beyond web, having a CMS that wants to own the front-end becomes more of a burden than a benefit, hence the rise of the “headless” or “de-coupled” CMS. Multiple SaaS vendors have sprung up over the last few years, creating a Content-as-a-Service market which I’ve blogged about before.

Drupal has been able to expose its content and other operations via a RESTful API for quite a while. But in those early days it was not quite as simple as it could be. If you have a team, for example, that just wants to model some content types, give their editors a nice interface for managing instances of those types, and then write a front-end that fetches that content via JSON, you still had to know a fair amount about Drupal to get everything working.

Last summer, Acquia, a company that provides enterprise support for Drupal headed up by Drupal founder, Dries Buytaert, released a new distribution of Drupal called Reservoir that implements the “headless CMS” use case. Reservoir is Drupal, but most of the pieces that concern the front-end have been removed. Reservoir also ships with a JSON API module that exposes your content in a standard way.

I was curious to see how well this worked so I grabbed the Reservoir Docker image and fired it up.

The first thing I did was create a few content types. Article is a demo type provided out-of-the-box. I added Job Posting and Team Member, two types you’d find on just about any corporate web site.

My Team Member type is simple. It has a Body field, which is HTML text, and a Headshot field, which is an image. My Job Posting type has a plain text Body field, a Date field for when the job was posted, and a Status field which has a constrained list of values (Open and Closed).

With my types in place I started creating content…

Something that jumped out at me here was that there is no way to search, filter, or sort content. That’s not going to work very well as the number of content items grows. I can hear my Drupal friends saying, “There’s a module for that!”, but that seems like something that should be out-of-the-box.

Next, I jumped over to the API tab and saw that there are RESTful endpoints for each of my content types that allow me to fetch a list of nodes of a given type, specific nodes, and the relationships a node has to other nodes in the repository. POST, PATCH, and DELETE methods are also supported, so this is not just a read-only API.

Reservoir uses OAuth to secure the API, so to actually test it out, I grabbed the “Demo app” client UUID, then went into Postman and did a POST against the /oauth/token endpoint. That returned an access token and a refresh token. I grabbed the access token and stuck it in the authorization header for future requests.

Here’s an example response for a specific “team member” object.

My first observation is that the JSON is pretty verbose for such a simple object. If I were to use this today I’d probably write a Spring Boot app that simplifies the API responses further. As a front-end developer, I’d really prefer for the JSON that comes back to be much more succinct. The front-end may not need to know about the node’s revision history, for example.

Another reason I might want my front-end to call a simplified API layer rather than call Drupal directly is to aggregate multiple calls. For example, in the response above, you’ll notice that the team member’s headshot is returned as part of a relationship. You can’t get the URL to the headshot from the Team Member JSON.

If you follow the field_headshot “related” link, you’ll get the JSON object representing the headshot:

?

The related headshot JSON shown above has the actual URL to the headshot image. It’s not the end of the world to have to make two HTTP calls for every team member, but as a front-end developer, I’d prefer to get a team member object that has exactly what I need in a single response.

One of the things that might help improve this is support for GraphQL. Reservoir says it plans to support GraphQL, but in the version that ships on the Docker image, if you try to enable it, you get a message that it is still under development. There is a GraphQL Drupal module so I’m sure this is coming to Reservoir soon.

Many of my clients are predominantly Java shops–they are often reluctant to adopt technology that would require new additions to their toolchain, like PHP. And they don’t always have an interest in hiring or developing Drupal talent. Containers running highly-specialized Drupal distributions, like Reservoir, could eventually make both of these concerns less of an issue.

In addition to Acquia Reservoir, there is another de-coupled Drupal Distribution called Contenta, so if you like the idea of running headless Drupal, you might take a look at both and see which is a better fit.

(Live/Online)..Wilder vs Ortiz Full Fight Live On Free

Drupal News Org - Fri, 03/02/2018 - 18:44

(Live/Online)..Wilder vs Ortiz Full Fight Live On Free

Revel

Drupal Themes - Fri, 03/02/2018 - 18:31

(Live/Online)..North Carolina vs Duke Live Stream Free 2018

Drupal News Org - Fri, 03/02/2018 - 18:30

(Live/Online)..North Carolina vs Duke Live Stream Free 2018

=================================================

=================================================
North Carolina vs Duke Live Stream  Total Sportek

Drupal version: Drupal 4.5.x or older

(Live/Online)..Deontay Wilder vs Luis Ortiz Fight Live Stream Free TV Showtime Boxing 2018

Drupal News Org - Fri, 03/02/2018 - 18:00

(Live/Online)..Deontay Wilder vs Luis Ortiz Fight Live Stream Free TV Showtime Boxing 2018.[Full/Fight] Deontay Wilder vs Luis Ortiz Live Stream FREE TV.[Full/Fight] Deontay Wilder vs Luis Ortiz Live Stream FREE TV

Drupal version: Drupal 4.5.x or older

Mediacurrent: Friday 5: 5 Ways to Secure Your Drupal Site

Main Drupal Feed - Fri, 03/02/2018 - 16:23

Happy Friday Everyone! On the eve of the Drupal Drive-in, happening tomorrow in Charolette North Carolina, we welcome Mark Shropshire to the show to talk about his favorite topic, Drupal Security!
 

YG Agency

Drupal Themes - Fri, 03/02/2018 - 13:18

Coming soon!!

orkjerns blogg: Updating to Drupal 8.5 with composer

Main Drupal Feed - Fri, 03/02/2018 - 12:03
Updating to Drupal 8.5 with composer admin Fri, 03/02/2018 - 12:03

If you are like me, you might have already started planning the upgrade to Drupal 8.5, now that the first release candidate is out. It's awesome by the way, among other things, thanks to the incredible work done with layout builder. And if you are more like me, you are managing your sites with composer. Then, depending on the rest of your project, you might (also like me), have encountered some initial problems upgrading to Drupal 8.5

Having hit my fair share of composer oddities with running the Violinist.io composer monitor and upgrade service, I wanted to compile a couple of error messages along with solutions, to the folks struggling with this out there.

Installation request for webflo/drupal-core-require-dev (locked at 8.4.5, required as ~8.4) -> satisfiable by webflo/drupal-core-require-dev[8.4.5].

If you have installed an out of the box version of https://github.com/drupal-composer/drupal-project, this might be an error message you encounter. Full error message, for reference:

./composer.json has been updated > DrupalProject\composer\ScriptHandler::checkComposerVersion Loading composer repositories with package information Updating dependencies (including require-dev) Your requirements could not be resolved to an installable set of packages. Problem 1 - webflo/drupal-core-require-dev 8.4.5 requires drupal/core 8.4.5 -> satisfiable by drupal/core[8.4.5] but these conflict with your requirements or minimum-stability. - webflo/drupal-core-require-dev 8.4.5 requires drupal/core 8.4.5 -> satisfiable by drupal/core[8.4.5] but these conflict with your requirements or minimum-stability. - webflo/drupal-core-require-dev 8.4.5 requires drupal/core 8.4.5 -> satisfiable by drupal/core[8.4.5] but these conflict with your requirements or minimum-stability. - Installation request for webflo/drupal-core-require-dev (locked at 8.4.5, required as ~8.4) -> satisfiable by webflo/drupal-core-require-dev[8.4.5]. Installation failed, reverting ./composer.json to its original content.

The reason this fails is that the project you have created is depending on the dev packages for drupal core, which are tied to a specific version of core. So to update core, we also need to update the dev packages for core.

The solution to this is pretty simple:
Open your composer.json file and replace the lines for drupal/core and webflo/drupal-core-require-dev with the following:

"drupal/core": "~8.5" // ...and "webflo/drupal-core-require-dev": "~8.5"

Afterwards you can go ahead and run:

composer update drupal/core webflo/drupal-core-require-dev --with-dependencies Installation request for symfony/config (locked at v3.2.14) -> satisfiable by symfony/config[v3.2.14].

This probably comes from the fact that you also have some other packages depending on this specific Symfony package in your project. Like drush or drupal console. Here is a full error message, for reference:

Loading composer repositories with package information Updating dependencies (including require-dev) Your requirements could not be resolved to an installable set of packages. Problem 1 - Conclusion: don't install drupal/core 8.5.0-rc1 - Conclusion: don't install drupal/core 8.5.0-beta1 - Conclusion: don't install drupal/core 8.5.0-alpha1 - Conclusion: don't install drupal/core 8.6.x-dev - Conclusion: remove symfony/config v3.2.14 - Installation request for drupal/core ~8.5 -> satisfiable by drupal/core[8.5.0-alpha1, 8.5.0-beta1, 8.5.0-rc1, 8.5.x-dev, 8.6.x-dev]. - Conclusion: don't install symfony/config v3.2.14 - drupal/core 8.5.x-dev requires symfony/dependency-injection ~3.4.0 -> satisfiable by symfony/dependency-injection[3.4.x-dev, v3.4.0, v3.4.0-BETA1, v3.4.0-BETA2, v3.4.0-BETA3, v3.4.0-BETA4, v3.4.0-RC1, v3.4.0-RC2, v3.4.1, v3.4.2, v3.4.3, v3.4.4]. - symfony/dependency-injection 3.4.x-dev conflicts with symfony/config[v3.2.14]. - symfony/dependency-injection v3.4.0 conflicts with symfony/config[v3.2.14]. - symfony/dependency-injection v3.4.0-BETA1 conflicts with symfony/config[v3.2.14]. - symfony/dependency-injection v3.4.0-BETA2 conflicts with symfony/config[v3.2.14]. - symfony/dependency-injection v3.4.0-BETA3 conflicts with symfony/config[v3.2.14]. - symfony/dependency-injection v3.4.0-BETA4 conflicts with symfony/config[v3.2.14]. - symfony/dependency-injection v3.4.0-RC1 conflicts with symfony/config[v3.2.14]. - symfony/dependency-injection v3.4.0-RC2 conflicts with symfony/config[v3.2.14]. - symfony/dependency-injection v3.4.1 conflicts with symfony/config[v3.2.14]. - symfony/dependency-injection v3.4.2 conflicts with symfony/config[v3.2.14]. - symfony/dependency-injection v3.4.3 conflicts with symfony/config[v3.2.14]. - symfony/dependency-injection v3.4.4 conflicts with symfony/config[v3.2.14]. - Installation request for symfony/config (locked at v3.2.14) -> satisfiable by symfony/config[v3.2.14].

The solution here is to indicate you also want to update this package, even if it's not specifically required. So if the failing command was the following:

composer update drupal/core --with-dependencies

Go ahead and change it to this:

composer update drupal/core symfony/config --with-dependencies

If you have other error messages, I would be glad to help out with a solution, and post the result here.

Credits

Thanks to zaporylie for looking into this with me, and to Berdir for pointing out the fact that core is not the package that requires symfony/config.

Let's finish this post with an animated gif of a composer

Wim Leers: API-First Drupal: what's new in 8.5?

Main Drupal Feed - Fri, 03/02/2018 - 11:11

Now that Drupal 8’s REST API 1 has reached the next level of maturity, I think a concise blog post summarizing the most important API-First Initiative improvements for every minor release is going to help a lot of developers. Drupal 8.5.0 will be released next week and the RC was tagged last week. So, let’s get right to it!

The REST API made a big step forward with the 5th minor release of Drupal 8 — I hope you’ll like these improvements :)

Thanks to everyone who contributed!

  1. text fields’ computed processed property exposed #2626924

    No more need to re-implement this in consumers nor work-arounds.

    "body":{ "value":"<p>Hi!</p><script>alert('foo')</script>", "format":"basic_html" }

    "body":{ "value":"<p>Hi!</p><script>alert('foo')</script>", "format":"basic_html", "processed":"<p>Hi!</p>" }
  2. uri field on File gained a computed url property #2825487

    "uri":{"value":"public://cat.png"} ⬇ "uri":{"url":"/files/cat.png","value":"public://cat.png"}

  3. Term POSTing requires non-admin permission #1848686

    administer taxonomy permission ⬇ create terms in %vocabulary% permission

    Analogously for PATCH and DELETE: you need edit terms in %vocabulary% and delete terms in %vocabulary%, respectively.

  4. Vocabulary GETting requires non-admin permission #2808217

    administer taxonomy permission ⬇ access taxonomy overview permission

  5. GET → decode → modify field → encode → PATCH → 403 200 #2824851

    You can now GET a response, modifying the bits you want to change, and then sending exactly that, without needing to remove fields you’re not allowed to modify. Any fields that you’re not allowed to modify can still be sent without resulting in a 403 response, as long as you send exactly the same values. Drupal’s REST API now implements the robustness principle.

  6. 4xx GET responses cacheable: more scalable + faster #2765959

    Valuable for use cases where you have many (for example a million) anonymous consumers hitting the same URL. Because the response is not cacheable, it can also not be cached by a reverse proxy in front of it. Meaning that we’ll have hundreds of thousands of requests hitting origin, which can bring down the origin server.

  7. Comprehensive integration tests + test coverage test coverage

    This massively reduces the risk of REST API regressions/changes/BC breaks making it into a Drupal 8 release. It allows us to improve things faster, because we can be confident that most regressions will be detected. That even includes the support for XML serialization, for the handful of you who are using that! We take backwards compatibility serious.
    Even better: we have test coverage test coverage: tests that ensure we have integration tests for every entity type that Drupal core’s stable modules ship with!
    Details at API-First Drupal — really!. Getting to this point took more than a year and required fixing bugs in many other parts of Drupal!

Want more nuance and detail? See the REST: top priorities for Drupal 8.5.x issue on drupal.org.

Are you curious what we’re working on for Drupal 8.6? Want to follow along? Click the follow button at REST: top priorities for Drupal 8.6.x — whenever things on the list are completed (or when the list gets longer), a comment gets posted. It’s the best way to follow along closely!2

The other thing that we’re working on for 8.6 besides the REST API is getting the JSON API module polished to core-worthiness. All of the above improvements help JSON API either directly or indirectly! More about that in a future blog post.

Was this helpful? Let me know in the comments!

Thanks to Ted for reviewing a draft of this blog post! And sorry for not changing the title to API First Drupal in 8.5.0: Amazing progress because of tedbow’s work on setInternal properties!!!!!!!!! even though that would’ve been totally accurate :D

For reference, historical data:

  1. This consists of the REST and Serialization modules. ↩︎

  2. ~50 comments per six months — so very little noise. ↩︎

  • API
  • Acquia
  • Drupal

OPTASY: From Drush Clear Cache to... Rebuilding Cache in Drupal 8: What's the Difference?

Main Drupal Feed - Fri, 03/02/2018 - 10:45
From Drush Clear Cache to... Rebuilding Cache in Drupal 8: What's the Difference? radu.simileanu Fri, 03/02/2018 - 10:45 From "remorsefully clearing all Drupal cache using Drush, to actually... rebuilding them in Drupal 8? Why the change? How will the new “cache-rebuild” concept impact your Drupal development process? All your troubleshooting and site updating sessions?

(Live/Online)..Arsenal vs Manchester City Live Stream Free Soccer Premier League 2018

Drupal News Org - Fri, 03/02/2018 - 08:47

(Live/Online)..Arsenal vs Manchester City Live Stream Free Soccer Premier League 2018. Arsenal vs Manchester City Live Stream Total Sportek Watch every Arsenal match live streaming links here for the 201718 season vs Everton Norwich City Swansea Tottenham and. Arsenal vs Man City LIVE team and lineup news weather latest and. Manchester City travel to face Arsenal in the Premier ...

tgyjgnu

Drupal News Org - Fri, 03/02/2018 - 08:19

yjumnhmj

(Live/Online)..Portugal vs Australia 2018 Live Stream Free TV Watch Soccer 2018

Drupal News Org - Fri, 03/02/2018 - 06:29

(Live/Online)..Portugal vs Australia 2018 Live Stream Free TV Watch Soccer 2018

=================================================
CLICK HERE=> Watch Soccer 2018 Live Stream FREE TV
-----------------------------------
CLICK HERE=> Watch Soccer 2018 Live Stream FREE TV
=================================================

Country comparison Portugal vs Australia 2018 | countryeconomy com
https:  countryeconomy com countries compare portugal australia

Country comparison, you can compare any two countries and see the data side by side  Here you have the comparison between Portugal vs Australia 2018
[Live] Portugal vs Australia 2018 Live Stream soccer Coverage Tv    
https:  txcatholic org     live-portugal-vs-australia-2018-live-stream-soccer-coverage-t   

10 hours ago - [Live] Portugal vs Australia 2018 Live Stream soccer Tv Coverage Online  Date: TODAY Description: Live Scores – CAF Champions League: Portugal vs Australia   Live Scores – CAF Champions League: Portugal vs Australia Live Scores – CAF Champions League: Portugal vs Australia   Portugal vs    
Portugal vs  Australia - 2 March 2018 - Soccerway
https:  my soccerway com matches 2018 03 02 world     portugal australia 2724412

Portugal matches  Competition: All; Friendlies Women; Algarve Cup; UEFA Women's Championship; Women's WC Qualification Europe  Show: All; Home; Away  « Previous Next »    
Portugal vs Australia :: Algarve Cup 2018 :: Match Events :: thefinalball   

Drupal version: Drupal 4.6.x

Pages