Unexplainable Errors After Starting to Make Theme

1) Ensure that you placed your new theme in /sites/all/themes/
If that /themes folder isn't there, then create it & put your custom/contributed themes within. While this shouldn't be the reason for your errors, it's a "best practices" approach to including contributed/custom themes (& modules). Besides it being a best practices approach, it'll save you hours of hair-pulling when you have to upgrade Drupal core (i.e. not having to touch the /sites folder).

2) Clear all caches

These 2 should get you on the right path.

Miguel Hernandez - www.migshouse.com
Founder & CEO - The OpenMindz Group
Writer- Linux Journal & TechZulu

One more thing to add:

Is the folder name of your theme exactly what you called your .info file? (i.e. litmus, same case?)

High Rock Media | Drupal Photography | Skype: highrockmedia | Twitter

As the error messages indicate the name of your theme is missing from the .info file.
Please double check the .info file, maybe you accidentally delete or commented out the 'name = Litmus' line from that (comments are started with semicolons in .info files).

I tried both and received the same errors you mentioned above.

br - phpro

I've seen similar errors when my .info files (for modules in this case, but I imagine it applies equally to themes) were saved on a Windows machine and then uploaded to a Linux server.

Re-creating the files in the native editor on Linux (nano, vi, etc.) fixed the errors for me. Saving them in a compatible format (ANSI in Notepad++ seems to work) should also suffice.

@acy76 I'd guess your right. The carriage return that Windows saves in a document is \R. Linux uses \N as a carriage return. If you save a document in Windows without checking your format, you'll get runtime errors, especially with PHP.

Carriage return and UTF8 format is very important, but in my case converting from Win (CR and LF) to Unix (only LF) format wasn't enough.

I had to add one line of comment at top of .info file, e.g. "; comment".

I was making Bartik subtheme and this eventually worked. Strange.

--
Polish Drupal Forum - http://drupal.pl
personal site - http://palikowski.net
tutorials site - http://elimu.pl

This problem can also occur in the case of bad formatted .info file inside the theme. So another thing you can try is:

1. Delete the existing .info file of the theme. (Or rename it if you want to save your settings).
2. Create a new .info file from scratch. Put in minimum required info - name, description, core - and see if it works.
3. If yes, start adding your settings from the old .info file and check your theme constantly to see where it bumps again, IF it does. It didn't for me. :)

This problem was caused while developing a D7 theme on a Windows machine. I guess it's somewhat related to what @jessebeach and @acy76 mentioned.

Hope it helps. Happy theming!

Sandu Camerzan

I experienced the "Undefined index: name in system_sort_modules_by_info_name()-errors", when i was following the theming guide for the Zen-theme. (The readme.txt file)
To Subtheme Zen, one has to copy a sample STARTERKIT folder and rename the folder and an info file, to the new subthemes name. After i did that i got approx. 10 "Undefined..." errors. When i removed the subthemes folders, all worked fine again.

After trying to figure out, what went wrong i finally discovered, that the owner of all the files in the subtheme was "root". The owner of the other drupal files, is someone else - lets call him "webu".
After changing the owner from "root" to "webu" all the errors disapeared.

Though all was able to read from the files when root was the owner - it apparently is not enough. The theme system must do some writing or executing, since it did not work with readable rights.

The reason for the errors are, that many like I, upload a theme through Drupals Themesystem. This will work with the proper rights, because it is the web-user that does the filework. When i copy a folder - i typically log ind with ssh, and there i am another user - in this case root.

Hope this helps others, with this problem

I had this when creating a sub-theme from Marinelli.

All my drupal files are owned by "drupal" and the web server runs as "apache".

Once I changed the group of all files to "apache" and made sure they were all group-writable, the problem went away.

Hi! I had the same problems. In my case there were gulp folder with .info file in it. Drupal thinks that that file is about new theme. I removed this folder and deleted MySQL string about that "theme".

Regards!

• jessebeach
• adrian

• Arabic
• Alappuzha
• Event Platform
• Western Ohio User Group
• Goa Drupal Community
• Liverpool
• Chandigarh Drupal Geeks (C.D.G.)
• API-First Working Group
• Compony opinionated developers
• 4SPOTS