Skip to content

Some modifications I made to the latest organice #1030

@simmule-turner

Description

@simmule-turner

I recently made these changes and wanted to know if folks are interested. For most of the changes I borrowed extensively from other issues, where possible. I use the repeating timestamps, capture changes, and the visibility cycling extensively. Below are the changes that I have made in the last few weeks:

Release Notes

  • Added more "raw" entries in capture template variables.
    • %AC create header and append to the description (defined by the header path in the capture template)
    • %AD append to the description (defined by the header path in capture template)
    • %C - Number of lines (a counter) in description, only used (available) with %AC or %AD.
    • %L month - Jan, Feb ... Dec
    • %M month - 01, 02, ..., 12.
    • %d day - 01, 02, ..., 31.
    • %e day of the week - Sun, Mon, ..., Sat.
    • %H hour - 00 ... 12 ... 23.
    • %m minutes - 00 ... 59.
  • Added repeating timestamps for #978.
  • Added visibility cycling, extracted & modified from #509
  • Added capture to description - extracted & modified from #936, possibly resolves #934. An example template to append to a table in the description would be:
%AD|%?|%y-%M-%d|%H%m|

  • Added capture to new header and append to description. An example template to create daily journal entries would be:
%AC%y-%M %L^%y-%M-%d
+ %H:%m - %?

  • Added header and internal links (CUSTOM_ID property links). Resolving #990 and #879?
  • Added inline images, globally in settings, or #+STARTUP: inlineimages or #+STARTUP: noinlineimages (highest priority). Resolving #113.
  • Added comment (#), will not show headline in Agenda or Task List, unless ignoreComment is set. Resolves #971?
  • Added archiving will not show in Agenda or Task List, if ARCHIVE tag is set unless ignoreArchive is set. Resolves #971?
  • Fixed export #1036 to use depth first and work with :ARCHIVE: tag.

  • update nginx.default nextcloud to support CORS, then nextcloud can be used for storage. Addressed CORS issue for my nextcloud installation #1046.
# Nextcloud -- add CORS support for organice
server {
  listen <listen-port>;

  location / {
    proxy_pass http://localhost:<passthrough-port>;
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Host $server_name;
    proxy_set_header X-Forwarded-Proto https;
    proxy_set_header X-Forwarded-For $remote_addr;
    client_max_body_size 0;

    add_header 'Access-Control-Allow-Origin' '*' always;
    add_header 'Access-Control-Allow-Methods' 'GET,OPTIONS,POST,PROPFIND,PUT,DELETE' always ;
    add_header 'Access-Control-Allow-Headers' 'Origin,Accept,X-Requested-With,Content-Type,Access-Control-Request-Method,Access-Control-Request-Headers,Authorization,X-CSRF-Token,Depth' always;

    if ($request_method = 'OPTIONS') {
      return 204;
    }
  }

  location = /.well-known/carddav {
    return 301 $scheme://$host/remote.php/dav;
  }

  location = /.well-known/caldav {
    return 301 $scheme://$host/remote.php/dav;
  }
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions