<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Installing Omeka in a Local Sandbox on a Mac (OS 10.8)</title>
	<atom:link href="http://mith.umd.edu/engl668k/?feed=rss2&#038;p=1387" rel="self" type="application/rss+xml" />
	<link>http://mith.umd.edu/engl668k/?p=1387</link>
	<description>ENGL 668K at the University of Maryland</description>
	<lastBuildDate>Mon, 12 Jun 2017 13:00:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5</generator>
	<item>
		<title>By: zenius</title>
		<link>http://mith.umd.edu/engl668k/?p=1387#comment-677923</link>
		<dc:creator>zenius</dc:creator>
		<pubDate>Sun, 28 May 2017 01:47:02 +0000</pubDate>
		<guid isPermaLink="false">http://mith.umd.edu/engl668k/?p=1387#comment-677923</guid>
		<description><![CDATA[its great,,, I Like it.......]]></description>
		<content:encoded><![CDATA[<p>its great,,, I Like it&#8230;&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: baltlokis</title>
		<link>http://mith.umd.edu/engl668k/?p=1387#comment-637813</link>
		<dc:creator>baltlokis</dc:creator>
		<pubDate>Mon, 29 Aug 2016 14:15:08 +0000</pubDate>
		<guid isPermaLink="false">http://mith.umd.edu/engl668k/?p=1387#comment-637813</guid>
		<description><![CDATA[like it]]></description>
		<content:encoded><![CDATA[<p>like it</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gifari</title>
		<link>http://mith.umd.edu/engl668k/?p=1387#comment-538390</link>
		<dc:creator>Gifari</dc:creator>
		<pubDate>Sat, 09 May 2015 07:28:33 +0000</pubDate>
		<guid isPermaLink="false">http://mith.umd.edu/engl668k/?p=1387#comment-538390</guid>
		<description><![CDATA[Nice , i can try my own omeka and if i want my local omeka to online setting is same or i have to change something ? Sorry I&#039;m still a beginner in this case]]></description>
		<content:encoded><![CDATA[<p>Nice , i can try my own omeka and if i want my local omeka to online setting is same or i have to change something ? Sorry I&#8217;m still a beginner in this case</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Westgard</title>
		<link>http://mith.umd.edu/engl668k/?p=1387#comment-105473</link>
		<dc:creator>Josh Westgard</dc:creator>
		<pubDate>Thu, 31 Oct 2013 15:17:17 +0000</pubDate>
		<guid isPermaLink="false">http://mith.umd.edu/engl668k/?p=1387#comment-105473</guid>
		<description><![CDATA[Hello Mesut, Turning on error reporting is the way to go.  If you are using a Mac (which I assume since this post was written for Mac users!) then you might not be able to find the .htaccess file because it is classed as a &#039;hidden&#039; file by the OS.  To see the hidden files in a directory you can use the command &quot;ls -a&quot; while in the directory in your terminal window. To toggle the visibility of hidden files in the Finder, you can use the following command in the terminal:
&lt;code&gt;defaults write com.apple.finder AppleShowAllFiles &#039;1&#039;&lt;/code&gt;
Then restart the finder with:
&lt;code&gt;killall Finder&lt;/code&gt;
To toggle back to invisibility of those files, do:
&lt;code&gt;defaults write com.apple.finder AppleShowAllFiles &#039;0&#039;&lt;/code&gt;
and then restart Finder with the above command.
There are also instructions for toggling the visibility of hidden files in the finder on this Apple Support page: https://discussions.apple.com/message/1923151#1923151
I also recommend asking for help on the Omeka forums: http://omeka.org/forums/]]></description>
		<content:encoded><![CDATA[<p>Hello Mesut, Turning on error reporting is the way to go.  If you are using a Mac (which I assume since this post was written for Mac users!) then you might not be able to find the .htaccess file because it is classed as a &#8216;hidden&#8217; file by the OS.  To see the hidden files in a directory you can use the command &#8220;ls -a&#8221; while in the directory in your terminal window. To toggle the visibility of hidden files in the Finder, you can use the following command in the terminal:<br />
<code>defaults write com.apple.finder AppleShowAllFiles '1'</code><br />
Then restart the finder with:<br />
<code>killall Finder</code><br />
To toggle back to invisibility of those files, do:<br />
<code>defaults write com.apple.finder AppleShowAllFiles '0'</code><br />
and then restart Finder with the above command.<br />
There are also instructions for toggling the visibility of hidden files in the finder on this Apple Support page: <a href="https://discussions.apple.com/message/1923151#1923151" rel="nofollow">https://discussions.apple.com/message/1923151#1923151</a><br />
I also recommend asking for help on the Omeka forums: <a href="http://omeka.org/forums/" rel="nofollow">http://omeka.org/forums/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mesut Mert</title>
		<link>http://mith.umd.edu/engl668k/?p=1387#comment-105254</link>
		<dc:creator>Mesut Mert</dc:creator>
		<pubDate>Wed, 30 Oct 2013 23:01:36 +0000</pubDate>
		<guid isPermaLink="false">http://mith.umd.edu/engl668k/?p=1387#comment-105254</guid>
		<description><![CDATA[I followed all the steps, I installed ImageMagick with the old fashioned method but at the end I always end up with the same expression on the screen: &quot;Omeka has encountered an error&quot;
I could not manege to see the problem because I cannot find the .htaccess file. 
Any ideas?]]></description>
		<content:encoded><![CDATA[<p>I followed all the steps, I installed ImageMagick with the old fashioned method but at the end I always end up with the same expression on the screen: &#8220;Omeka has encountered an error&#8221;<br />
I could not manege to see the problem because I cannot find the .htaccess file.<br />
Any ideas?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Westgard</title>
		<link>http://mith.umd.edu/engl668k/?p=1387#comment-8538</link>
		<dc:creator>Josh Westgard</dc:creator>
		<pubDate>Thu, 28 Mar 2013 19:10:43 +0000</pubDate>
		<guid isPermaLink="false">http://mith.umd.edu/engl668k/?p=1387#comment-8538</guid>
		<description><![CDATA[Another addendum: Step 4, installing Imagemagick, seems to be a sticking point for a lot of people installing Omeka for the first time.  My thought was that cactuslab.com&#039;s easy installer would avoid such problems, but no dice.  Despite having tried out various paths to ImageMagick, I could only get it working properly after I installed it the old fashioned way.  I&#039;m appending the basic procedure below, which unfortunately involves a number of preliminary steps:

1. Install the Xcode developer tools from the Mac App Store. Once that is done, install the command line tools for Xcode: https://developer.apple.com/xcode/ (follow the link for additional developer tools).

2. Install MacPorts from here: http://www.macports.org/install.php

3. Once you&#039;ve got Macports installed, you can use it to install imageMagick by running the following command at the command line: $ sudo port install ImageMagick (see also http://www.imagemagick.org/script/binary-releases.php#macosx).

I had hoped that my instructions for installation with the much less complicated cactuslab.com installer (step #4 above) for ImageMagick would work, but in the end I&#039;ve had to revert to the old fashioned method to get Omeka up and running. Once you&#039;ve installed ImageMagick this way, the path listed in step one of the previous addendum should work.]]></description>
		<content:encoded><![CDATA[<p>Another addendum: Step 4, installing Imagemagick, seems to be a sticking point for a lot of people installing Omeka for the first time.  My thought was that cactuslab.com&#8217;s easy installer would avoid such problems, but no dice.  Despite having tried out various paths to ImageMagick, I could only get it working properly after I installed it the old fashioned way.  I&#8217;m appending the basic procedure below, which unfortunately involves a number of preliminary steps:</p>
<p>1. Install the Xcode developer tools from the Mac App Store. Once that is done, install the command line tools for Xcode: <a href="https://developer.apple.com/xcode/" rel="nofollow">https://developer.apple.com/xcode/</a> (follow the link for additional developer tools).</p>
<p>2. Install MacPorts from here: <a href="http://www.macports.org/install.php" rel="nofollow">http://www.macports.org/install.php</a></p>
<p>3. Once you&#8217;ve got Macports installed, you can use it to install imageMagick by running the following command at the command line: $ sudo port install ImageMagick (see also <a href="http://www.imagemagick.org/script/binary-releases.php#macosx" rel="nofollow">http://www.imagemagick.org/script/binary-releases.php#macosx</a>).</p>
<p>I had hoped that my instructions for installation with the much less complicated cactuslab.com installer (step #4 above) for ImageMagick would work, but in the end I&#8217;ve had to revert to the old fashioned method to get Omeka up and running. Once you&#8217;ve installed ImageMagick this way, the path listed in step one of the previous addendum should work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Westgard</title>
		<link>http://mith.umd.edu/engl668k/?p=1387#comment-8095</link>
		<dc:creator>Josh Westgard</dc:creator>
		<pubDate>Wed, 27 Mar 2013 14:23:42 +0000</pubDate>
		<guid isPermaLink="false">http://mith.umd.edu/engl668k/?p=1387#comment-8095</guid>
		<description><![CDATA[Addenda: 

1. With respect to step 11 above, when configuring your Omeka installation the path for ImageMagick should be /opt/local/bin/.

2. Should Omeka complain upon first launch, you may find it helpful to activate error reporting using the procedure outlined here: http://omeka.org/codex/Retrieving_Error_Messages]]></description>
		<content:encoded><![CDATA[<p>Addenda: </p>
<p>1. With respect to step 11 above, when configuring your Omeka installation the path for ImageMagick should be /opt/local/bin/.</p>
<p>2. Should Omeka complain upon first launch, you may find it helpful to activate error reporting using the procedure outlined here: <a href="http://omeka.org/codex/Retrieving_Error_Messages" rel="nofollow">http://omeka.org/codex/Retrieving_Error_Messages</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
