Themes for 2.0

[Jessica DeSpain]

I am trying to develop a demo prior to an NEH grant deadline of December 6, and I was wondering if there was anyway that I might be able to get the files for a basic theme prior to the new release so that I could get a head start on CSS modification. If so, please e-mail me at jde...@siue.edu.

[Jeremy Boggs]

Assuming you have a working instance of Omeka 2.0 somewhere, the only files you actually need in a theme are:

· css/style.css

· theme.ini

Themes in Omeka will use the core templates found in application/views/scripts, unless your theme specifically includes any. So, by adding 'css/style.css' to your theme, Omeka will load that file instead of the one in application/views/scripts. See "Understanding Default Theme Files" at http://omeka.org/codex/Understanding_Default_Theme_Files for more info.

You can see a full list of these templates for Omeka 2.0 at https://github.com/omeka/Omeka/tree/master/application/views/scripts. Omeka 2.0 is still under development, so I'm not sure how stable the templates (and the functions they use) are at the moment. If you regularly pull updates from the master branch, you should be able to keep up with changes just fine, and incorporate changes into any additional templates you'd want to override in your theme. (This is a case where it's handy to watch the "History" of a particular directory through Github, like https://github.com/omeka/Omeka/commits/master/application/views/scripts). Otherwise, just edit the css/style.css file in your theme, and rely on the core template files for everything else.

Best,

Jeremy

On Oct 13, 2012, at 5:28 PM, Jessica DeSpain wrote:

I am trying to develop a demo prior to an NEH grant deadline of December 6, and I was wondering if there was anyway that I might be able to get the files for a basic theme prior to the new release so that I could get a head start on CSS modification. If so, please e-mail me at jde...@siue.edu.

--
You received this message because you are subscribed to the Google Groups "Omeka Dev" group.
To view this discussion on the web visit https://groups.google.com/d/msg/omeka-dev/-/eRLbzcts6Z4J.
To post to this group, send email to omek...@googlegroups.com.
To unsubscribe from this group, send email to omeka-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/omeka-dev?hl=en.

[Jessica DeSpain]

Thanks, Jeremy. I am getting really close to getting a working version of Omeka 2.0 up and running but I am getting stuck on what should be a fairly easy step. I'm using XAMPP. I've unzipped Omeka in htdocs, and added my info to my db.ini file. Now, when I go to make it read/writable using terminal, for some reason it is telling me the directory doesn't exist. I am using cd Applications/XAMPP/xamppfiles/htdocs/omeka. I get "no file or directory". Am I make an elementary mistake?

[John Flatness]

On Wed, 2012-10-17 at 10:10 -0700, Jessica DeSpain wrote:
> Applications/XAMPP/xamppfiles/htdocs/omeka.
>
If you pasted that exactly as you entered it, it looks like you just
forgot the leading slash:

/Applications/XAMPP/xamppfiles/htdocs/omeka

[Jessica DeSpain]

Nevermind, I got it! 

On Saturday, October 13, 2012 4:28:06 PM UTC-5, Jessica DeSpain wrote:

[Jessica DeSpain]

Thanks,John, I did forget the slash. I'm trying to install 2.0 on a Mac with xampp. I've gone in to rename all of the changeme files. I've added the database and changed by db.ini file. For some reason though when I go to localhost/Omeka I am getting an Omeka error message rather than the install page. When I changed .htaccess to allow for error messages I received a server error 500. I tried to troubleshoot using past Omeka forums (double-checking my db.ini file against phpmy admin, for example), but for whatever reason, I can't seem to get around the error message. Any suggestions?

[Jessica DeSpain]

So, I figured out the problem, which was related to the writability of the files file (which used to be archive). For some reason the numerical scripts already posted in documentation weren't working, but I finally had luck with chmod -R 7777 files. Thank you for all of your help today!