List position

I have no idea what version of Drupal I have and I am new to this.
I have a catalog page with items for sale. They are displayed in rows and each row has 3 items across.
I would like to sort the order of these items. The list position doesn't seem to work. I think I have most of them set
at position 0 and it says if they have the same position they will be sorted alphabetically but mine just appear in the order they were uploaded.
Thanks for the help.

PO and POT files

This page gives an introduction to POT and PO files.

Drupal uses the .po (portable object) and .pot (portable object template) extensions for the translation files. These use the GNU Gettext format. The basic difference between these file formats is that .pot files are simply templates which contain no translations while .po files do.

PO files

PO files are the files which contain the actual translations. Each language will have its own PO file, for example, for French there would be a fr.po file, for german there would be a de.po, for American English there might be en-US.po. You can even use po files to customise the displayed text without changing the code, by for example, creating an adapted file such as en-my_company.po.

The core of each PO file is very simple; it is made of simply pairs of the source text - that which is found in the code - and target text, the text which is wanted in the translation. For example, in the French PO file you might have a translation of a string as follows:

msgid "Hello world"
msgstr "Bonjour le monde"

The msgid contains the text actually in the code, and the msgstr contains the text into which it is translated. If there is no translation given in the msgstr, then the default msgid string will be displayed.

Where to get Drupal templates?

Iv been looking around and found a couple different websites like,, and but I am not sure which to go for... anyone know of a good site that is really trustworthy and that has great support when you need it.

Agile Unit Testing

What You Should Know

This book page is not for developers new to application testing; therefore, it does not describe unit testing concepts and techniques. The following list describes the level of experience or knowledge required to understand this book:

  • Familiarity with unit tests, programming on PHP 5.x with the corresponding development tools for that platform, and the process of writing tests in general.
  • A general understanding of the structure and concept of xUnit testing frameworks; the object model; dependency management (composition, inheritance patterns) including database mocking.

Agile testing combines engineering with testing activities into one activity and can be expressed by following Test Driven Development where a developer would write tests first. In particular, this book page focuses on unit testing where units represent objects or single architectural layers in contrast to functional testing (customer tests) where a unit represents the complete application (many architectural layers). Functional testing is also vitally important to Drupal but the focus of a separate book page.

Why to Isolate - Focus on Unit Tests

How to work on a patch that is not yet in core, but is needed as base cleanly

For twig we had the problem that the basic patch was not accepted, but that the followup issues should be clean.

The idea is to use two patches within one.

What do you do if you happen to find a patch with two patches in one?

Patch contributors

For patch contributors the workflow is not that difficult to the regular patches:

Assuming origin is the "core" repository and you work in feature branches the workflow is:

Lets further assume the patch is in issue 1806546 with comment number 4

Getting a clean branch:

# update core
git fetch origin
# checkout 8.x branch
git checkout origin/8.x
# checking out an issue feature branch with comment number
git checkout -b core-1806546-4

Applying the current patch:

wget .../patch.diff
# this directly _commits_ the patches, conflicts are resolved like
# with rebase / merge
git am patch.diff
# Now you fork again with your new comment number
git checkout -b core-1806546-5

Now you add your changes and then you do:

# this updates the original patch and can be done as often as you want
git commit --amend .
# this creates the new 2-part patch
git format-patch -M --stdout origin/8.x > mynewpatch.diff
# this creates the interdiff
git format-patch -M --stdout core-1806546-4 > interdiff.txt

Debugging platform creation

Unable to download

Error message:

Unable to download XXXXX from XXXXX.                             [error]
ERROR: Platform not created successfully.

#1517134: D6 ERROR: Platform not created successfully

This sort of thing could easily be caused by network problems, and is probably outside the control of kPlatforms.

The -f switch allows us to pass Drush Make the --force-complete option, so that we're not back at square one when trying to build these platforms.

Another useful tool for making these downloads faster, easier and more reliable is to use a proxy cache such as Squid. This avoids having to download the same packages multiple times, as we have to do when building both Drupal and CiviCRM platforms, for example. Also, in the case of a failure during a platform build, it will maintain cached copies of all the projects that downloaded successfully. More documentation is available here: Using a proxy cache to accelerate platform builds.

"Invalid version" and "Non-existent project type"

Error messages:

Project information for XXXXX retrieved. [ok]
Invalid version XXXXX for XXXXX. [error]


Subscribe with RSS Subscribe to RSS - Drupal 8.x