When an app on your iPhone, iPod Touch, or iPad is behaving an an unexpected way, our Support Humans may ask you to send along a Console Log. The log can tell us exactly what is going on behind the scenes and help get you back up and running quickly. In order to get the Console Log from your device, you'll need to download a special utility.
Step 1: Download and install the iOS Console application
LemonJar makes a free application called iOS Console, which is very handy for retrieving console logs from an iPhone, iPad or iPod Touch.
Step 2: Connect your iOS Device
Launch iOS Console and plug your device into your computer. After a few moments, a window should appear that displays the console log.
Step 3: Copy the Console Log to an email
Copy and paste the console results in a reply to a message from the Support Human you're working with. We'll do the rest! If you get stuck at any point, don't forget that you can reach us by phone at +1 800-315-6664 between 10am and 5pm PST/PDT (GMT-8/GMT-7).View Article
As of May 2013, we've introduced OmniPresence support to our document-based iPad apps, so that they can automatically sync documents via a WebDAV server — such as our own free Omni Sync Server. You can access the same documents on your desktop or laptop by installing OmniPresence for Mac.
If you don't already have a free Omni Sync Server account, you can sign up for one here.
Setting up OmniPresence in OmniOutliner 2 for iOS and OmniGraffle 2 for iOS
- Open OmniOutliner or OmniGraffle to the document picker. Tap Locations at the top left to back out to the list of available file locations.
- Tap Add Cloud Account, then Add Omni Sync Server Account and enter your sync credentials.
- Tap Save to test the credentials and finish the account configuration process.
After the compatibility check is complete, you’ll be able to tap the new Server folder in the file location list. To move files from Local Documents to your OmniPresence cloud folder:
- Open the Local Documents location, then tap Select in the toolbar.
- Tap to select the documents you’d like to move.
- Tap the folder icon in the toolbar, then Move to "(OmniPresence folder name)". The files will be moved from Local Documents to your cloud sync folder.
Setting up OmniPresence in OmniOutliner for iPad (v1), OmniGraffle for iPad (v1), and OmniGraphSketcher for iPad
- Tap the Local Documents title in the toolbar and choose Cloud Setup, then Add Omni Sync Server Account.
- Enter your Omni Sync Server login information, and be sure that OmniPresence is checked. (If not, the server will act as remote storage instead of actively syncing updates and changes).
- When you're ready, tap Connect. The app will do some compatibility checks, and then your new folder will be connected to the cloud.
After connecting you'll find yourself looking at an empty cloud folder. To move files from Local Documents to your OmniPresence cloud folder:
- Tap the title in the toolbar and choose Local Documents.
- Tap Edit in the toolbar, and tap to select the documents you'd like to move.
- Tap Share, then Move to "(OmniPresence folder name)". The files will be moved from Local Documents to your cloud sync folder.
Staying in Sync
Files stored in an OmniPresence-enabled folder will sync automatically whenever changes are made to them. To stop syncing a file, just move it back to Local Documents. To disconnect a synced folder, go to Cloud Setup and tap Edit to delete the folder from your list of OmniPresence accounts. Note that this won't delete any remaining contents of the folder; the files will remain in the cloud, but won't be affected by changes on this device.
The OmniPresence button appears in the toolbar when viewing a synced folder in the document browser as well as when editing a document in a synced folder. It animates to indicate a sync is in process, and if needed you can tap it to prompt a sync as well.
"Where are my files?"
If you connect to your Omni Sync Server account using Finder or a third-party WebDAV client, you most likely will not see anything. This is because OmniPresence stores your sync data in a hidden folder.
"What's the difference between Local Documents and my OmniPresence folder?"
Local Documents are files on your iPad that will not sync. Any files in this location can only be directly modified from the iPad.
Files in an OmniPresence folder automatically sync with the server. If you don't have an internet connection, previously-downloaded files are still accessible offline from your iPad, and any changes you make to these documents will be communicated with the server on your next sync. If you delete or otherwise remove a document from the OmniPresence folder on one device, it will be removed from your sync folder on other devices.View Article
The Omni Group has a long history of offering upgrade pricing on new versions of existing apps, and while the App Store doesn't support selective discounts, we originally planned on letting Mac App Store customers move to our own store to get those discounts. Unfortunately, we discovered that as long as we continue to sell our apps through the Mac App Store, we are not allowed to distribute updates through other channels to apps which were purchased from the App Store.
The new Standard edition of OmniFocus is $39.99, with an in-app purchase option to activate Professional features like AppleScript and custom perspectives. All App Store customers who’ve purchased OmniFocus 1 will receive that in-app purchase for free, granting them the Pro feature set for the price of Standard (which happens to be half the price of OmniFocus 1). For step-by-step instructions on upgrading, please see the "Mac App Store" section of this article: Buying an Upgrade for OmniFocus 2.
Because we've switched to an in-app purchase to add Professional features like AppleScript, Visio import and export, and more, OmniGraffle 6 starts at $99.99 in the App Store. If you have OmniGraffle 5 Standard or Pro installed via the Mac App Store—it must be via the Mac App Store, not ours—we can offer discounts based on prior purchases. No matter where you purchased, there's more info on how to get your discount on this page: Buying an Upgrade for OmniGraffle 6.
When the Mac App Store opened, we promised that OmniOutliner 4 would be a free upgrade for anyone purchasing version 3 from that point on. OmniOutliner 4 was released as a free update to Mac App Store customers.View Article
Please note: due to the wide array of possible setup configurations and outside factors involved with custom hosting setups, troubleshooting, setting up, or administering WebDAV servers is beyond the scope of the tech support we are able to provide.
IMPORTANT: When you expose files and folders on your computer to the internet (even with password protection), you assume some risk. These steps assume that you're familiar with the Apache web server and understand this risk. You should be comfortable with the responsibilities of maintaining a server, including keeping your Mac up to date with the latest security patches. These instructions are offered as guidance for those interested in self-hosting, but should not be considered a comprehensive overview of the Apache implementation process.
Setting up WebDAV without Server.app
OS X Server includes WebDAV as one of the options for file sharing. However, this WebDAV implementation is a fairly complex configuration that utilizes a proxy to create Apache processes that run as user accounts. In our experience this configuration has had a number of hard-to-identify bugs that can corrupt your data. We don't recommend using it at this time.
Instead of using OS X Server's built-in file sharing WebDAV configuration, we recommend manually configuring a WebDAV share by editing the appropriate Apache configuration file. This requires some knowledge of both the Apache web server and Apple's implementation. You should also be comfortable with the command line. This configuration will emulate Apple's configuration by allowing you to login to a WebDAV share using system account credentials. You will also be able to use posix group permissions to control access to the shares. However, all files and folders must be owned by the Apache web server (_www) since this configuration will use the web server's account to read/write all files.
For more information about the Apache httpd server, see the excellent documentation on apache.org
There is an overview of Apple's configuration of the Apache httpd server see their documentation website. While Apple's documentation is sparse, they do outline what directories are used for configuration files, which is a great place to start poking around.
Take particular note of Apple's ReadMe.txt file (
/Library/Server/web/config/Apache2/ReadMe.txt). It goes into more operational details about what they've configured and what you may and may not touch.
Assuming that you have never used Apple's built-in file sharing feature to host WebDAV configuring Apache is fairly straightforward.
Make a copy of the example WebDAV configuration file and move it to OS X Server's website configuration directory. The example configuration file is located at:
Copy this file to the website configuration path with a new filename. In this case we chose omnipresence-dav.conf but you can name it whatever makes the most sense to you.
cp /etc/Apache2/original/extra/httpd-dav.conf /Library/Server/Web/Config/apache2/sites/omnipresence-dav.conf
Note: any file that you put in /Library/Server/Web/Config/apache2/sites/ that ends in “.conf” will be included by OS X Server in the Apache configuration when the Websites service is started. If your configuration file has any errors in it the Apache service will not start.
The example configuration file outlines how a WebDAV share is defined. We will edit it to define a single share called “omnipresence” that uses OS X's user and group accounts to control access. Remove the example configuration's Directory directive block and replace it with your own configuration. It should look like our example omnipresence share that we've configured below:
# Map the URL /omnipresence to the filepath that we want to host a WebDAV share. Alias /omnipresence "/Volumes/System/Users/Shared/OmniPresence/" # Turn on WebDAV sharing and only allow user accounts in the posix group “staff” to access it. <Directory "/Volumes/System/Users/Shared/OmniPresence/"> Dav On Order Allow,Deny Allow from all # Use Open Directory for authentication. AuthType Digest Require group maxgeekery </Directory>
Note: the _www user, which is the posix account that Apache runs as, must have read and write access to to the WebDAV share.
For more information about Alias, Directory, and Dav directives in Apache configuration files see the following Apache documentation sections.
Also, be sure to understand the processing of Order directives so that you don't accidentally make your WebDAV share readable (or writable!) to the rest of the Internet:
Starting the Service
When you are satisfied with your configuration, start the Websites service and test your new WebDAV share to make sure that it is accessible and that the permissions are correct!
If, by chance, you previously enabled WebDAV on file shares using OS X's File Sharing service you will need to turn it off. This may be harder than it sounds! On some versions of OS X Server (before Mavericks) turning off WebDAV in the File Sharing service in Server.app did not, in fact, turn off WebDAV sharing. While the WebDAV share will no longer allow client access it still creates httpd processes that respond to client connections. This could cause conflicts with other WebDAV shares that you may want to setup. In our test case, we had to unload the serverd launchd job and then load it back for OS X Server to stop creating Apache processes running Apple's WebDAV configuration. For some reason, even reboots of the system did not change the WebDAV sharing state.
To stop and then start serverd use launchctl
% sudo launchctl unload /Library/LaunchDaemons/com.apple.serverd.plist % sudo launchctl load /Library/LaunchDaemons/com.apple.serverd.plist
Only unload and load the serverd process if, after turning WebDAV sharing off, you notice processes that are still configured as WebDAV shares and a reboot of the system does not clear them. Note that these processes only appear if a client tries to access the server system with those user's credentials. So, after a fresh reboot the system may look clear, but double check by watching the processes on the system while a client connects.
Example processes you should not see after turning off Apple's WebDAV share. The account maxgeekery is a user account on the system.
% ps aux |grep http ~ maxgeekery 3128 0.0 0.0 2432784 628 s002 S+ 6:29PM 0:00.00 grep http maxgeekery 3117 0.0 0.0 2462048 1392 ?? S 6:29PM 0:00.00 /usr/sbin/httpd -f /Library/Server/Web/Config/apache2/httpd_webdavsharing_template.conf -D FOREGROUND -k start maxgeekery 3116 0.0 0.0 2453856 2460 ?? Ss 6:29PM 0:00.07 /usr/sbin/httpd -f /Library/Server/Web/Config/apache2/httpd_webdavsharing_template.conf -D FOREGROUND -k start
You may also see other httpd processes running as root or _www. You can safely ignore them in this context.
_www 3089 0.0 0.0 2509032 2996 ?? S 6:29PM 0:00.01 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/apache2/httpd_server_app.conf root 3083 0.0 0.0 2456696 5016 ?? Ss 6:29PM 0:00.09 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/apache2/httpd_server_app.conf _www 3118 0.0 0.0 2492648 2880 ?? S 6:29PM 0:00.01 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/apache2/httpd_server_app.conf
Our applications are distributed in two different ways: the storefront on our website, and the Mac App Store. These apps are functionally identical, aside from the way that they're licensed. Apps purchased through our storefront require a license in order to run, whereas Mac App Store versions do not; they instead are tied to the Apple ID you used to purchase.
In order to determine where your app came from, open the Menu Bar and take a look at the contents. Omni Store menu options will include the Check for Updates… and Licenses… options. On the other hand, Mac App Store copies will lack these options, and potentially reference an In-App Purchase… if applicable.