I am trying to find a MediaWiki bot or extension that would do the following:
I sometimes copy external content to MediaWiki to display it in proper context and to make it searchable. That is not very DRY.
I would like to keep a live link to the original content using a special tag and have a bot update the MediaWiki page if the original content changes.
For instance, the snippet could be a configuration file in Subversion that I want to reference in documentation. I would like to do something like:
<external-content
url="http://svn/config.txt"
start="#begin snippet"
end="#end snippet">
</external-content>
The MediaWiki bot would download http://svn/config.txt, retain everything between the #begin snippet and #end snippet comments, and paste the result right between the external-content tags.
This way I can be sure that as I change the config.txt, my MediaWiki documentation stays in sync.
There are numerous other uses. I am not looking only into referencing Subversion content, there are many other web-based systems with data I would like to integrate in this manner.
Does anyone know of a bot that would do this?
You could probably do this with a MediaWiki parser tag extension. In fact, the "Include" extension seems to do something very much like what you're asking for.
Related
I have a large number of existing MS Word documents I want to import into tiki-wiki, but some of these include images that don't carry over into the editor (including the WYSIWYG editor).
I'm looking for some plugin or setting that would allow me to copy-paste images into the tiki-wiki editor that automatically uploads images to the file gallery and insert the image in place. Converting the documents to HTML code is one solution I have found to retain the images and Word documents, but removes the ability to easily edit the wiki pages.
I have looked and cannot seem to find anything like this. In fact, many members of the wiki community seem to be against such a feature. Has anyone found a plugin or workaround for this issue?
Sorry, that's not a feature in Tiki currently, it would be great if it was (i'm surprised anyone seemed to be against it, we always welcome volunteers and sponsors if you're willing to code or commission it!)
We are planning to migrate to markdown over the next few versions, so maybe add this as a feature request as part of that? The planning page is here https://dev.tiki.org/WYSIWYG-and-Markdown
To preface this I'm not an ExactTarget expert.... We use ExactTarget and are interested in more archiving our email newsletters so that our subscribers can later use our articles as a reference. We have an archive folder set up in the exact target system, but that is not customer-facing and contains things like extra code.
As I understand it, the current process for archiving involves taking screenshots of the email that is sent out which is stitched together as a PDF. The PDF's are then stuck behind a password protected folder on a website.
Obviously, this is a hacky/low-tech way to do this.
Are there any ways to export these mails for archival purposes that people are using?
I am guessing from the above that you are using the premade templates and creating content using the Exact Target WYSIWYG editor. From there I am assuming also that these articles are in content boxes and HOPEFULLY each 'article' is in a single content box.
If so, then your best bet is to go to the HTML tab on this box and copy that code there and have this inserted onto your company blog (or website if you do not have a blog). Your network admin or website designer will likely know the best way to insert these snippets of code to fit the layout and navigation of the site.
If your message is not personalized, or if so you mdke a generic recipient in your list, you may be able to use the 'view as webpage' link to get the source code. Not sure if those links expire after X days or something though.I have never tried this or tested, but on most email sends there is a "view as webpage" link, maybe try taking one of these links and either hosting on your blog/site or using that link as a reference for your customers.
Using a PDF or screen shots is far from optimal as the content becomes an image and loses a lot of value.
Hope this helps.
I've recently installed the Microsoft Office Word Add-in For MediaWiki (http://www.microsoft.com/en-us/download/details.aspx?id=12298) and I'm able to save MediaWiki files just fine but I can't open them (they are opened as plain text).
How can I force MS Word to make the correct association for MediaWiki files?
You can't. "Interpreting" the MediaWiki markup, i.e. wikitext, is called parsing. Writing a MediaWiki parser is a pain and there is no single parser which fully works yet, other than MediaWiki itself. LibreOffice's wiki-publisher plugin and those which copied it are able to produce good wikitext from their well-formed data format, but making this bidirectional is another matter.
Parsoid is almost perfect now and produces standard HTML, but it's a rather heavy application, you can't expect it to be embedded in Word. Maybe someone can write a LibreOffice plugin for Parsoid, though! Would be scary, but who knows.
See https://www.mediawiki.org/wiki/Alternative_parsers for more information. Many tried and got hurt. :)
The view file macro allows embedding documents (.ppt, .pdf, etc) on a Confluence wiki page. Limitation is, documents must be on attachments.
So question, is there a way to load dynamically a file located into an SCM's deposit?
P.S. Current SCM: Perforce.
UPDATE: As I see, there is no official Perforce plugin.
You may of course include a link to that file, if Perforce provides a way to link items. We use that a lot, to include content that is stored in Subversion, and document the standing, the usage, ... in Confluence then. The user has to click on that link to get that file, but I think it is necessary anyway, because your authorization rules are not known to Confluence.
I have a web app project that I will be starting to work on shortly. One of the features included is going to be a content management system where users can add content and then that content will be combined with a template and then output as a regular .html file. This .html file would then be FTPed to their own web host.
As I've always believed in not reinventing the wheel I figured I'd see if there are any quality customizable CMSes out there that do this already do this. For instance, Blogger.com allows you to post all of your content to your account there; but offers the option to let you use your own hosting. Any time you publish a new article then a new .html page is generated (as well as an updated index page with links to the new article) and then the updated content is FTPed to your own server.
What I would like is something like this that I can modify to more closely suit my needs.
Required Features:
Able to host on my own server
Written in PHP
Users add content through their account, then when posted it is FTPed as .html to their server
Any appropriate pages are also updated to link to the new content (like the index page or whatnot)
Templateable
Customizable
Optional (but very much desired) features:
Written in CodeIgniter or a similar PHP framework
While CodeIgniter isn't strictly required, I would very much prefer it. It speeds up development time and makes things much easier to implement.
So - any suggestions? I've stumbled across a few CMSes that push to remote servers as static pages, but the ones I've found all are hosted on the developers servers which means that I cannot modify it at all.
Adobe Contribute might work for your situation. A developer/designer creates a set of templates with Dreamweaver and publishes the templates. Authorized users can then create pages based on the templates and only make changes within the editable regions. It includes systems for drafts and reviews prior to publishing (via many options, including ftp) and incorporates automatic version control. It can work with static html pages or dynamic pages like php.
Sounds like you need a separate application that can do this for you.
For example, you should be able to write something that queries Drupal's menu router and saves the output (with curl) to a directory and then run's rsync to push your content where you want it to go.
Otherwise your requirements are likely to be outside the scope of a typical CMS. Separating this functionality will give you better options.
You'd need to write a filter for your URLs too. It's a bit of work...
Hope that helps!