Apps
Knowledge
People
Register
Login
APPS
-

FORUM
-


-
- Content .- Fans (12) .- Knowledge Base (6) . 

Shorty

   0.3.25  

ownCloud Productivity

Score 82%
arkaschaarkascha
Home
Shorty
zoom

Shorty
zoom

Shorty
zoom

Version Control:  Link
Depends on  ownCloud 5
Downloads:  5387
Submitted:  Apr 25 2012
Updated:  Apr 30 2013

Description:

Shorty offers a service to store, manage and use a collection of short links pointing to resources in the web. The features are a combination of a centralized bookmarks collection, an URL shortener and a basic access control. A new Shorty can be created either manually by entering a URL ("New shorty") or by simply clicking the "Shortlet" whenever you come over a page you want to share. This "Shortlet" is something like a Bookmarklet, a script based bookmark meant to be stored inside the bookmark area of your web browser. When clicked, the page currently open in the browser will be added to your collection of Shortys, including a practical shortened URL.

Each Shorty contains a source and a target URL. The source URL can be used to be posted in forums, sent inside an email message or whatever. It is typically much shorter than the target URL, a full blown web URL, though this depends a little on which shortening service you want to use as a "backend". Basic access control is implemented to control the access of Shortys posted to forums or sent per email, but not on a per user or per group base. Existing Shortys can be blocked for usage, set to expire on a certain date and obviously can be removed permanently again.

There is an optional plugin to this app called 'Shorty Tracking':
http://apps.owncloud.com/content/show.php/Shorty+Tracking?content=152473
It records and displays each access of a Shorty which might help in maintainance.

A basic documentation is packed into several files in the 'doc' folder and also offered online:
Configuration: http://svn.christian-reiner.info/web/wsvn/shorty/branches/0.3/doc/CONFIGURATION




Changelog:

* Tue Apr 30 2013 Christian Reiner: version 0.3.25
Addional personal preference to set the default status for new Shortys.
Fixed a layout glitch for backend selection in the preference dialog.
Fixed controls panel positioning to comply with the FluXX Compensator (Y).
* Sun Mar 24 2013 Christian Reiner: version 0.3.24
Fixed shortlet not to result in an error when being used.
* Wed Mar 20 2013 Christian Reiner: version 0.3.23
Allow direct activation in ownCloud5 based installations.
* Fri Mar 01 2013 Christian Reiner: version 0.3.22
Some general security fix to the apps framework.
* Wed Feb 20 2013 Christian Reiner: version 0.3.21
Fixed visibility of list header which was accidentially hidden below the control panel.
Fixed display of feedback on actions by reimplementing the messenger area.
Added a new preference to control the level of verbosity of feedback on actions.
Optimized preference retrieval (caching strategy).
* Tue Feb 15 2013 Christian Reiner: version 0.3.20
Fixed decoding of titles when scraping meta data from target pages.
* Tue Feb 12 2013 Christian Reiner: version 0.3.19
Support for ownCloud version 5.
Fixed handling of favicons when adding multiple Shortys.
Update the favicon when a Shortys target url is changed.
Enhancement to the list layout and apeparance to improve readability.
* Mon Jan 14 2013 Christian Reiner: version 0.3.18
Fixed the 'recycle' icon for rows marked as deleted, to not scrumble row layout.
Switched more (dynamically controlled) icons to svg format.
Fixed some problems in compatibility to ownCloud version 4.0 based installations.
Action icons now stay visible inside the active row when not hovering.
Size optimization for the png versions of icons.
* Mon Jan 07 2013 Christian Reiner: version 0.3.17
Use svg version of icons where applicable.
Recreated most icons for a more unified look and feel.
Fixed qrcode retrieval uder PostgreSQL database engines.
Generally prevent text and content selections except for input elements.
Numerous fixes to get Shorty usable under MS Internet Explorer.
* Tue Jan 01 2013 Christian Reiner: version 0.3.16
Fixed automatic text selection inside the usage popups.
Force downloading of a qrcode image when self referencing it.
* Mon Dec 31 2012 Christian Reiner: version 0.3.15
Changed supported OC version to 4.9 (OC-4.5).
Support for the postgresql database engine.
The apps top controls panel can be hidden now and got an enhanced layout.
Some style and layout corrections especially for webkit based browsers.
Fixed validation of the static backend setup for cross domain situations.
Better support for cross domain verification for the static backend configuration.
* Sat Dec 15 2012 Christian Reiner: version 0.3.14
Fixed big oops display of access times that gave the wrong month and day!
* Wed Dec 11 2012 Christian Reiner: version 0.3.13
Fixed layout of share dialog getting distorted under certain circumstances.
* Thu Nov 29 2012 Christian Reiner: version 0.3.12
Fixed a small glitch in settings handling.
Some minor performance and logging enhancements.
* Fri Nov 16 2012 Christian Reiner: version 0.3.11
Fixed visualization of last access time inside Shorty dialogs.
Enabled forwarding to more http based protocol schemes: shttp, ipp, webdav, webdavs
* Tue Nov 01 2012 Christian Reiner: version 0.3.10
Some fixed to the actions inside dialogs when used inside OC-4.0.x installations.
An additional service 'shorty_stats' allows to remotely retrieve data.
* Fri Oct 26 2012 Christian Reiner: version 0.3.9
Targets of existing Shortys can be modified as an explicit action now.
Enhanced notification and exception visualization and handling.
A few bugfixes and enhancements for title handling inside Shortys.
Some further layout and style fixes, cleanups.
* Tue Oct 09 2012 Christian Reiner: version 0.3.8
Switched layout of list of shortys to a liquid style (using the whole screens width).
Fixed display size for some exotic favicons inside dialogs.
Internal style reorganisation to isolate OC4 backwards compatibility exceptions.
Fixed visualization of explanations for goo.gl backend in preferences dialog.
Fixed sharpness control of dialogs.
Fixed datepicker dialog sometimes being hidden by other widgets.
Some fixes for usage under MS Internet Explorer though still a lot of issues remain.
A few layout enhancements and german translation completion.
* Fri Sep 28 2012 Christian Reiner: version 0.3.7
Preparations to rely on the OC core to refresh the request token if implemented.
- the Shorty strategy and code is to be accepted into the OC core :-)
- for version prior to that Shorty still handles refreshing itself
Fixed a crash that was introduced by changes in the OC core in recent beta versions.
Some preparations for future referencing of files stored inside OC as opposed to URLs.
Some internal code changes to reflect advances in the underlying jquery library.
A few logical fixes to detection of special runtime exceptions.
Some more small optical layout fixes.
Fixed missleading debug statement in ajax hooks for settings and preferences control
Fixed settings and preferences control not to ignore empty values
* Sat Sep 09 2012 Christian Reiner: version 0.3.6
General appearance enhancements for some dialog details.
Clearified explanations and hints for preferences and settings.
Some internal changes required by the changes in the upcoming OC5 release:
- most visible change: the personal preferences moved to a popup dialog inside the Shorty app.
- convenient reference to the system settings from within the personal preferences of admin users.
- additional 'home page' button referencing the apps page in the OC app store.
* Sun Aug 12 2012 Christian Reiner: version 0.3.5
Fixed standalone dialogs not being visible in rare circumstances.
Some cleanups in the style rule selectors.
* Mon Aug 06 2012 Christian Reiner: version 0.3.4
Implementation of a runtime callback catalog to ease plugin development.
Internal code and namespace changes to match OCs Coding Style Guide.
Simplified retrieval of meta data for urls to work the same in all dialogs.
More flexible list filtering by using callbacks for column value retrieval.
Visible click count in Shorty and sums are live updated now when the source url is clicked.
Fixed the internal verification of the configuration of the static backend.
* Tue Jul 24 2012 Christian Reiner: version 0.3.3
Use OCs CSRF protection framework for ajax requests.
Fixed a few compatibility issues with OC5-pre versions.
* Thu Jul 19 2012 Christian Reiner: version 0.3.2
Fixed a few problems with updating a currently listed Shorty after a modification.
Fixed storage of empty expiration dates when used with a MySQL database system.
* Mon Jul 18 2012 Christian Reiner: version 0.3.1
Fixed sanity checks in registration of actions inside the plugin interface.
Fixed highlighting of freshly added entries in lists (flashing).
Some internal recoding to remove depreciated library methods.
Fixed updating of Shortys in the list right after changing them.
Further enhancements in support of plugins
Rewritten and enhanced handling of clicks on Shortys.
* Sun Jul 15 2012 Christian Reiner: version 0.3.0
Implementation of a plugin interface including a partly redesign:
this enables plugins to register actions and thus enhance Shortys features.
Some internal code and comment cleanups.
* Fri Jul 13 2012 Christian Reiner: version 0.2.8
Some optical corrections to the share dialog.
Updated static backend configuration in doc files.
* Thu Jul 05 2012 Christian Reiner: version 0.2.7
Enhandements of the share dialog to get a clearer appearance.
Fixed removal of Shortys belonging to a user deleted inside ownCloud.
* Thu Jun 28 2012 Christian Reiner: version 0.2.6
Complet reimplementation of usage popups (optical and technical).
Per default suppress ssl certificate validation in backend communication.
Some IE specific styles fixes, the whole UI was unusable before !
- this might help in case the goo.gl backend appears unusable.
- additional preference to force that validation.
Some additional explanatory hints in the sharing dialog.
* Thu Jun 21 2012 Christian Reiner: version 0.2.5
Fixed translation engine to be compatible with OC versions > 4.0.2
A few minor linguistic corrections
* Sat Jun 16 2012 Christian Reiner: version 0.2.4
Fix of a false positive whilst verification of the static backend base.
Offering the 'Shortlet' now when showing an empty list.
Minor improvements to background logging.
Minor gui improvements.
* Sat Jun 09 2012 Christian Reiner: version 0.2.3
Bugfix for the routines generating shorty ids.
Fixes for usage under MS Windows platforms using php-5.4.
* Wed Jun 06 2012 Christian Reiner: version 0.2.2
Added swallowing of accidential outputs during ajax requests.
This protects the replies JSON struction from being corrupted.
Additional server side log entries on level INFO
* Sat Jun 02 2012 Christian Reiner: version 0.2.1
Fixed broken Shortlet
* Fri Jun 01 2012 Christian Reiner: version 0.2.0
Support of ownCloud version 4 (app interface incompatible to prior versions)
Additional status 'private' for Shortys only accessible for the owner himself
Rudimentary SMS support for smart phones (more an assistance, can be disabled)
Additional QRCodes to publish Shorty source URLs on the web (or elsewhere)
Data migration support as introduced by OC4
Cleanup of Shortys upon user account deletion
* Sun May 28 2012 Christian Reiner: version 0.1.6
Activation of Shorty sharing via SMS.
Enhanced backend descriptions.
* Sat Apr 28 2012 Christian Reiner: version 0.1.5
Target URL verification is less strict now, this way also more 'exotic' URLs notations are accepted.
A few changes to the initilization scripts to prevent race conditions at startup.
Changed URL specification in the Shortlet to prevent conflicts with a serverside suhosin protection.
* Fri Apr 27 2012 Christian Reiner: version 0.1.4
Visualization of busy state in dialogs while fetching meta data from targets.
* Fri Apr 27 2012 Christian Reiner: version 0.1.3
Prevented untimely submission of dialogs before having validated their contents.
* Fri Apr 27 2012 Christian Reiner: version 0.1.2
Fixed race conditions during initialization.
* Thu Apr 26 2012 Christian Reiner: version 0.1.1
Minor appearance corrections
* Wed Apr 25 2012 Christian Reiner: version 0.1.0
First official release.
* Tue Apr 24 2012 Christian Reiner: version 0.0.9
Initial release.
Buggy, but some parts actually working.




License: AGPL
Send to a friend
Subscribe
Other  Apps  from arkascha
Report inappropriate content

goto page: prev   1  2  3  4 

-

 Default / Force

 
 by drsbaitso on: Feb 13 2013  
Score 50%
drsbaitsodrsbaitso

Is there a way to force the users to use your built-in backend? FE, I want all users to only use the static backend.


Reply to this

-
.

 Re: Default / forced backend

 
 by arkascha on: Feb 13 2013  
Score 50%
arkaschaarkascha
Home

With built-in backend you mean the Static Backend, I guess.

The answer is no, there currently is no means to set a backend as the default or even force its usage. It is up to the users choice which of the available backends is used.

Actually the question has never been raised before. I hesitate to add more and more confguration options to the app. Setup is already far to complex. ownCloud is mean to be easy to setup and use.
Two options come to mind: reduction of the list of offered backends to those explicitly enabled inside the administration and using one single backend as the default. Both are separate aspects. The combination of both options would allow to enforce a backends usage. But as said: I hesitate...


Reply to this

-

 YOURLS backend

 
 by mdim on: Mar 6 2013  
Score 50%
mdimmdim
Home

Hi here,

I'd just like to express my +1 support in adding the support for YOURLS backend. I have my own instance of YOURLS, and the domain it is at is shorter than the domain of my ownCloud instance. Therefore, there would be two benefits for me to have an ability to use YOURLS backend in Shorty:

1) All short links would be available through a single nice interface (YOURLS)
2) Short URLs from the YOURLS instance would be shorter than those URLs provided by Shorty.

I find it crucial to have control over my data. YOURLS is free software as well, it is a nice piece of software putting the user in control, so why not add support for YOURLS?


Reply to this

-
.

 Re: supporting YOURLS as backend

 
 by arkascha on: Mar 6 2013  
Score 50%
arkaschaarkascha
Home

* Hi and thanks for taking interest! *

I absolutely agree that short and clean looking shortened urls are helpful. That is the reason why I implemented support of different backends and all. I general it is possibe and actually pretty easy to add support for further backends, as long as they provide a usable API. After a short look at YOURLS I have the impression that a support should be possible.

* Advantages of YOURLS as a backend? *
However I would like to repeat my question about the advantages of that. Until now I did not get any reply to that question:
What are the advantages of supporting YOURLS compared to setting up a 'static backend' as Shorty already offers? Not sure if you tried to setup a 'static backend', but to me the generated short urls are very similar to what YOURLS offers. Which is not suprising, since both solutions, YOURS and Shorty are url shorteners. If you have configuration access to a short named domain , then why not simply use that as a relay for a static backend by configuring a redirection rule (3 lines) as explained in the configuration or in the setup dialog for the static backend?

* Issue with builtin validation *
There currently appears to be an issue with certain complex cross domain setups when it comes to the integrated validation of such a static backend in Shorty. I was not yet able to reproduce that problem, only heard about it from 2 or 3 sources.
But as written before I give the hint to try the configuration nevertheless. It works even without internal positive validation which might fail due to security issues in rare cases. So have a try with it.

* ownCloud version 5 *
That said I have to confirm that support for Shorty in the upcoming version 5 of ownCloud is implemented and functional. Except again for that builtin validation which actually is totally broken in OC-5 due to sharpened security rules in the ownCloud framework. I have not yet found a solution for this. So again I give the advice: setup a static backend, in case validation fails (which it will in OC-5 for _all_ cross domain setups), then still have a try with that configured backend. Chances are it simply works and is usable despite the failed validation.

* Back to your question *
In general it cetainly is possible to implement support for YOURLS as a backend. But I currently simply don't see any real advantage over Shortys builtin static backend. Which is why I did not implement it. Maybe someone points out a reason?

* Maintainership *
I also have to mention that I kind of stopped maintaining my ownCloud apps due to other projects taking my time. I currently have not yet found a new maintainer. So if someone wants to step up or just implement this additional backend support that is absolutely fine with me. The link to my repository is shown up in the description, just grab branch-0.3 and go for it. I will be happy to grant write access to anyone motivated!


Reply to this

-

 Re: supporting YOURLS as backend

 
 by mdim on: Mar 7 2013  
Score 50%
mdimmdim
Home

I stumbled upon Shorty only yesterday. So I read the documentation a little bit, and I have one key question: do you always have to have an intermediate URL, i.e. a "relay url"?

The reason to support YOURLS backend is very easy - URLs that my instance of YOURLS generates will never have a "key" (e.g. "4" in http://l.dimjasevic.net/4 ) of length 6 to 12 in my lifetime. On the other hand, all Shorty keys are of length 6 to 12, which makes YOURLS the winner hands down. And even if the user knows how to write the web server rewrite rules for the static backend, which is a big assumption, YOURLS still wins.

I mentioned it earlier: my ownCloud instance is on the domain that is longer than the one where the YOURLS instance is. That's another strong argument (in my case) for YOURLS.

As a side note, it would be handy if there was an option to create short URLs when sharing ownCloud files with a public link, just by checking the "Create short URL" option in the share dialog.


Reply to this

-
.

 Re: Creating Shortys for files shared by ownCloud

 
 by arkascha on: Mar 7 2013  
Score 50%
arkaschaarkascha
Home

I reply to this aspect in a separate comment, since there is no connection to YOURLS. You mention:

> it would be handy if there was an option to create short URLs when sharing
> ownCloud files with a public link, just by checking the "Create short URL"
> option in the share dialog.

I absolutely agree.
I tried to find a stable and usable solution for this some time back but failed. Back then ownClouds sharing feature was (and it still is) rapidly changing. There was (is) no easy means to hook some additional option into the existing dialog.
I put great hope in the "Share API" when it was announced, but it does not really help here, it works the other way round.

To put things short:
I failed to come up with a reliable and usable solution for this. So I stopepd the attempt. Sorry for that.
If someone steps forward and says: he, I've got an idea for this: Great! Go! As said before contributions are more than welcome!


Reply to this

-
.

 Re: Re: supporting YOURLS as backend

 
 by arkascha on: Mar 7 2013  
Score 50%
arkaschaarkascha
Home

Thanks again for the feedback, especially for taking the time to add some details...Thanks again for the feedback, especially for taking the time to add some details...
Let me comment on your points one by one:


>>> do you always have to have an intermediate URL, i.e. a "relay url"?
Yes, that is the way Shorty is designed. The reason is that Shorty does not only act as an input frontend to other url shortening services. That certainly would be easy to implement, however it would mean to give away control over your shortened urls. Those shortened urls are typically used to be posted in some forum or to be sent by email. You typically have no control over that url once it is sent out. Using Shorty this is different, you keep the control, and this is what ownCloud is about: staying in control.
Without that relay url inside Shorty and the "two steps" forwarding strategy a url once shortened by some external shortening service would directly be resolved to the target url. You cannot change or stop that when using a basic shortening service unless you use the advanced features a few service providers offer, sometimes on a paid base. Shorty allows to use the basic shortening services because they offer really short url results whilst still staying in control about where the final target url points to. That final target is actually never revealed to the backend shortening service, that one only knows about Shortys relay url. This also means Shorty allows you to change that targt url at a later point in time, for example to resolve to an updated document version or because you moved something. So in a way Shorty adds features not offered by the basic url shortenening services. I assume YOURLS offers these features too, but then why don't you just use YOURLS?

>>> [...] YOURLS [...] URLs will never have a "key" of length 6 to 12 [as Shortys do]
This is true, absolutely. A few characters less make a difference if you have to type those URLs in a unconvenient input device like for example some smartphone. There are indeed much better and easier to use shortening alternatives available for those. Most ownCloud users however will never type those urls. So what is much more important to them is that urls stay within a length that does not get broken when being displayed in mail and news clients. For this the urls Shorty generates are short enough.

Actually the first implementations of Shorty did use primitive incremental keys like most shortening solutions do. The advantage is a resulting short url that is indeed a few characters shorter than what Shorty generates. However this has a drawback which is why I changed it: those keys can be guessed. Whilst that is of little importantance for public available material it does make a difference in a multi user environment that cares for privacy. Most ownCloud installations offer accounts for many users. With a short key everyone could simply iterate over the keys and peek at urls shortened by other users. And although Shorty cannot really prevent guessing keys the more cryptic keys Shorty generates do offer some protection against curious readers.

>>> even if the user knows how to write the web server rewrite rules for the static backend, which is a big assumption, YOURLS still wins.

Some truth in that again, not everyone is able to configure a redirection rule. However I think it makes sense to take a closer look:

1.) someone who does not have the technical knowledge to do so.
I'd advise to keep things simple. Use one of the external backends offered inside Shorty like the "ti.ny" service. It simply works, the generated urls are short, resolution is reliable, nothing to install. And you stay in control over the resolution.
YOURLS is no alternative in such case, you'd have to install and configure that. I just doubt that really is easier than a 3 line redirection rule.

2.) someone whithout control over a short named domain he can use for shortening urls.
In that case one has to rely on some external backend anyway. YOURLS is not an alternative without a short named domain under your control.

3.) someone with an own YOURLS installation on a short named domain.
Great! However: I can't imagine someone who is able to setup and configure a YOURLS installation but is unable to configure that 3 line redirection rule to use Shortys static backend. Installing YOURLS requires much more effort and knowledge.

I know having to setup that external redirection rule is inconvenient. But it was the easiest solution I found if you do not want to use an external provider. In my eyes there is no real alternative. Installing YOURLS for this is a much bigger effort. And if you already have a private YOURLS installation - then just use it. No need for Shorty.

>>> my ownCloud instance is on a domain that is longer than the one where the YOURLS instance is

Sorry, but that is no argument at all. Shortys static backend allows to use that short domain name. You don't need YOURLS if you can use that short named domain.



All that said I'd like to make clear again that I have nothing really against supporting a YOURLS backend. Support should be pretty easy to implement. However I simply don't see any real advantage in using Shorty when you already have a YOURLS setup you use. So where is the motivation? It seems to me the strongest argument is: "well, it is possible, so let's do it". But where is the point in that?

If someone wants to contribute by implementing support for YOURLS as a backend:
Great! Welcome! Just drop me a note and we can get started.


Reply to this

-

 Re: supporting YOURLS as backend

 
 by mdim on: Mar 10 2013  
Score 50%
mdimmdim
Home

I have an YOURLS instance, and I have an ownCloud instance. I thought it'd be nice if they could work together, i.e. if it was possible to use the YOURLS instance within the ownCloud instance.

Your points about privacy are valid, and I agree with you.

For me, to install YOURLS was relatively easy since I found all the needed documentation online, and it was easy to follow it. On the other hand, I'm not that good with redirection rules.

Now I see Shorty is not what I've been looking for for ownCloud due to my wish to have a direct URL to original URL mapping without an intermediate layer. The reason why I don't want an intermediate layer is because the layer introduces additional complexity, and if I decide to move away from it one day, all my shortened URLs are gone.


Reply to this

-
.

 Re: Re: supporting YOURLS as backend

 
 by arkascha on: Mar 10 2013  
Score 50%
arkaschaarkascha
Home

Ok, it seems we do agree at most points in the end.

And you are absolutely right that in your special case Shortys strategy of a double forwarding using a relay url can pose problems if you decide to stop using Shorty in future. So indeed Shorty is not the best choice as a simple frontend for YOURLS.
I doubt adding such a behaviour to Shorty makes sense. To allow to suppress the usage of the relay url to gain a more direct forwarding as you need it would make Shorty overly complex and error prone.
Instead a really simple separate app for ownCloud might offer exactly what you are looking for. A simple frontend to an existing YOURLS installation. Maybe someone will implement something along this line as a getting-started-project.

arkascha


Reply to this

-

 Re: Re: Re: supporting YOURLS as backend

 
 by AVee on: Mar 26 2013  
Score 50%
AVeeAVee

I can see two use cases for yourls in Shorty. The first one is where the yourls instance is on a remote domain. I've got a short domain, with a yourls instance. But I'd happily allow an owncloud-running friend to use it.
Secondly, should Shorty ever get integrated more tightly into Owncloud for stuff like link sharing integration with a local yourls instance might start to make sense as well.

Implementing yourls might be a bit complicated compared to pure public services, you might need an api-key, you could have multiple yourls services etc.

Actually Shorty might be better served with generic support for 'custom' services where the user specifies the api url to use. This would be sufficient to support yourls and probably some others as well. At least some of the current backends could be served that way as well.


Reply to this

-
.

 Re: Re: Re: Re: supporting YOURLS as backend

 
 by arkascha on: Mar 26 2013  
Score 50%
arkaschaarkascha
Home

Thanks again for feedback and interest.

> The first one is where the yourls instance is on a remote domain.
> I've got a short domain, with a yourls instance.
> But I'd happily allow an owncloud-running friend to use it.

I don't see why using that short domain name requires YOURLS ontop of Shorty. That is exactly what the 'Static Backend' is for. Simply define a static redirection rule on that domains host for that user pointing to his ownCloud instance. Two lines, that's all. If you have multiple users inside one ownCloud instance you still need only a single redirection rule. You just need one static redirection rule for each ownCloud instance regardless of how many users use those. A single leading character in the url is enough to distinguish which rule to use even in such a complex setup.

> should Shorty ever get integrated more tightly into Owncloud for stuff like link
> sharing integration with a local yourls instance might start to make sense as well.

Such integration certainly would be great. I made three attempts of an implementation myself and failed. Maybe someone else has a better approach or maybe newer ownCloud versions will lend themselves better to such usage. We will see.
However I don't see what the benefits of an additional YOURLS instance should be in such case. Where is the difference to other cases?

> Implementing yourls might be a bit complicated compared to pure public services,
> you might need an api-key, you could have multiple yourls services etc.

Shorty already implements backends that require an API key or similar. That is not a problem.

> Actually Shorty might be better served with generic support for 'custom' services
> where the user specifies the api url to use. This would be sufficient to support
> yourls and probably some others as well. At least some of the current backends
> could be served that way as well.

Sounds interesting. But unfortunately the APIs differ between shortening services. This would mean that specifying an API to use in a generic manner would require some more effort than just a base url. In my eyes that would make using Shorty much more complex and error prone. Remember that every user, not only administrative accounts can select which backend to use personally. And in the end the list of easily available shortening services is very limited. One exception might be private services, maybe setup by a company for internal use. But then again, why not simply use Shortys 'Static Backend'?

--

Sorry, maybe I miss something. But I suggest you explore the options already offered by Shorty. I am quite confident that you will find the app is sufficient as far as backend support is concerned. And as said many times before: nothing against supporting more backends, implementation is pretty easy, contributions welcome. But I still don't see any real advantage of supporting YOURLS apart from 'it can be done'. It would make things much more complex without offering a real benefit.

Have fun!
arkascha

PS: please note that Shorty lives in ownClouds guthub repositories now. So contribution is really easy for everyone :-)


Reply to this

-
.

 Import of YOURLS

 
 by kaffeeringe on: Mar 21 2013  
Score 50%
kaffeeringekaffeeringe

I would love to have an import for YOURLS and a description of what to do on the former YOURLS Server.

So I run ownCloud on cloud.exmaple.com and YOURLS on xmpl.com - How can I export/import my existing short URLs? And how do I have to configure xmpl.com to keep the old short URLs working? I guess I have to add some ReWrite-rules to a .htaccess - But how?


Reply to this

-
.

 Re: Import of YOURLS

 
 by arkascha on: Mar 22 2013  
Score 50%
arkaschaarkascha
Home

Ok, thanks for feedback and request...

I doubt there is a clean solution for this. Certainly there is no such option implemented in Shorty.
The best approach I can think of is this:

- create a new entry in Shorty for each existing url in the YOURLS installation by copying the target urls one by one. Shortys "Shortlet" might come in handy for this...
- take care that all requests to short urls in the YOURLS web space are forwarded to the relay url generated for each new entry in Shorty. This can be done by means of the http server the YOURLS installation is based on, but it requires to setup a forwarding rule for each entry in a central configuration file or in a .htaccess style file if not possible otherwise.
- as an optional step it might make sense to create a "Static backend" as offered by Shorty using the existing YOURLS web space as anchor, since that already exists, is usable and typically has a short base url which is important for a Static Backend. Note that only one general forwarding rule is required to support such a Static Backend.

To construct these forwarding rules an export of Shortys database table should be very helpful, since it can act as a starting point to create a forwarding table. But you have to do that by hand. For the export you could actually use Shortys query service or you simply use a database client.
The final forwarding rules will have to take care that any request to an old short url targetting the YOURLS installation is forwarded to the corresponding relay url inside Shorty. That way old and new short urls will be resolved and all requests can be tracked inside Shorty using the optional plugin "Shorty Tracking". The YOURLS installation itself will not be required any longer.

It might be possible to implement something like a "migration assistant" into Shorty. But I doubt there are enough people who need that to justify the effort of a clean implementation. Espeically since setting up the forwarding rules still has to be done manually (though prepared).

I hope this helps!
Feedback always welcome!


Reply to this

-
.

 installing owncloud 5.0

 
 by elpedriyo on: Mar 31 2013  
Score 50%
elpedriyoelpedriyo

Could anyone tell me why does it appear this errors in the administration panel of owncloud, once I install it:

Fatal PHP Undefined variable: c_unique at /usr/lib/php/head.php#48 31 de marzo de 2013 19:51
Fatal PHP Undefined variable: c_unique at /usr/lib/php/head.php#48 31 de marzo de 2013 19:50
Fatal PHP Undefined variable: c_unique at /usr/lib/php/head.php#48 31 de marzo de 2013 19:50
Fatal PHP Undefined variable: c_unique at /usr/lib/php/head.php#48 31 de Marzo de 2013 21:51
Fatal PHP Undefined variable: c_unique at /usr/lib/php/head.php#48 31 de Marzo de 2013 21:51
Fatal PHP Undefined variable: c_unique at /usr/lib/php/head.php#48 31 de Marzo de 2013 21:51
Fatal PHP Undefined variable: c_unique at /usr/lib/php/head.php#48 31 de Marzo de 2013 21:51
Warning PHP curl_setopt_array() [<a href='function.curl-setopt-array'>function.curl-setopt-array</a>]: CURLOPT_FOLLOWLOCATION cannot be activated when safe_mode is enabled or an open_basedir is set at /home/veter903/public_html/unhuevodejuegos.es/owncloud/3rdparty/Sabre/DAV/Client.php#462


Reply to this

-
.

 Re: installing owncloud 5.0

 
 by arkascha on: Apr 7 2013  
Score 50%
arkaschaarkascha
Home

OK, sorry for the delay, been traveling...
Let's have a try to sort this one out :-)

Let's start with the situation first: to me it is not really clear what your situation actually is. You write:
> once I install it
Does that refer to ownCloud itself, or to the Shorty app? Further, I have no idea what
> /usr/lib/php/head.php
actually is. Certainly not part of the Shorty app and it also does not belong to the ownCloud core. So what is it?
Without knowing that and how it is involved in a request to your ownCloud installation it is hard to judge... Especially noone can say what that variable c_unique is without actually knowing that file.
The last entry suggests that you also have 'safe_mode' enabled in your php configuration. ownCloud requires that setting to be switched off. With enabled safe_mode it is merely impossible to have any data altered on the server side which clearly contradicts the purpose of the ownCloud suite. You should turn that setting off in your php configuration.

What certainly can be said is that aparently you have configured your php such that errors are displayed which should only be done for debugging purposes. For production use such display must be disabled inside the php configuration.

Unless I really missread your question these are all issues with your php setup and the general installation of ownCloud-5. So no connection to this Shorty app discussed here. If you cannot solve your issues with the suggestions above it probably makes sense to contact the general ownCloud mail list or take a look in the ownCloud issue tracker on github.
Good Luck!


Reply to this

-

 YOURLS backend support

 
 by dlwilliams on: Apr 27 2013  
Score 50%
dlwilliamsdlwilliams

The YOURLS backend has much finer-grained control over shortened links. It would be GREATLY beneficial if I was able to connect Shorty to my own instance of YOURLS.


Reply to this

-
.

 Re: YOURLS backend support

 
 by arkascha on: Apr 27 2013  
Score 50%
arkaschaarkascha
Home

Ok, this field has been discussed at length. As written before some simple, direct support should be easy to implement, but I currently see no sense in such thing.

If there are more advanced features in YOURLS (never used it myself) it would have to be checked if and how those features could be accessed from shorty and what benefit that would give. They will have to fit into Shortys UI and approach. A full support certainly would be more simple to do in a specialized owncloud app acting like a pure YOURLS frontend.

But I am open to a discussion: I suggest you convince me of the sense of a YOURLS support inside Shorty :-) Contact me in freenode irc, channel #owncloud, PM is ok if you feel like or use my email address you find inside the shorty scripts. This board is not good for discussions...


Reply to this

-

 Not working

 
 by turnerd10 on: May 2 2013  
Score 50%
turnerd10turnerd10

"A positive vaidation of a backend configuration is not required to use that backend."

How do you go about selecting the backend and using it then?


Reply to this

-
.

 Re: Not working

 
 by arkascha on: May 2 2013  
Score 50%
arkaschaarkascha
Home

Hi, thanks for feedback and interest!
And sorry for the current inconvenience about that backend validation. Here is what you do:

If you want to use a 'Static Backend' you just configure it (the base url) in the system administration under the 'Shorty' section. Then an additional entry 'Static Backend' will be available for all users inside their personal Shorty settings.
The builtin validation is not required for that. It is currently broken due to changes in the OC internal security strategy which I did not yet find find a way around... A typical example for efforts meant in a good way and indeed serving a good goal, but still being painful and annoying in a few circumstances. Indeed clicking on the url shown in the administration, which raises the builtin validation, will currently claim a failure. Just ignore that, the backend is offered and can be used nevertheless.
All you have to make sure is that the backend actually works as described in the explanation. Easiest way to test that is by just creating a Shorty and testing whether it is usable. Best is to make the test with another web browser (not being logged into your ownCloud) and preferably from a system somewhere outside your home/company network.

Have fun!

PS: still looking for volunteers for contributions. For example by implementing a fix for this issue! :-)


Reply to this

-

 Re: Re: Not working

 
 by turnerd10 on: May 2 2013  
Score 50%
turnerd10turnerd10

I appreciate your reply, "Then an additional entry 'Static Backend' will be available for all users inside their personal Shorty settings."

That entry just isn't showing up, I placed it in like you've said under the Admin section, validation did fail, but still isn't available as a choice.


Reply to this

-
.

 Selecting the 'Static Backend'

 
 by arkascha on: May 2 2013  
Score 50%
arkaschaarkascha
Home

Strange...
I just checked to be sure, and for me things work as expected and described...

May I point out the two different places mentioned:
- the configuration is done in the system wide administration. This is done once for all users and requires administrative rights.
- each user choses a backend to use for his Shortys in the Shorty apps preferences: click the cog wheel at the far right in Shortys top control panel.

If there really is an issue I would love to know details about that. Either open an entry in ownclouds issue tracker or just ping me on freenode irc, channel #owncloud. Hope you sort things out ;-)


Reply to this

goto page: prev   1  2  3  4 

Add commentBack




-
 
 Who we are
Contact
Register
Explore
Apps
Knowledge
People
Participate
Add App
Public API
About apps.ownCloud.com
Legal Notice
Report Abuse
 

Copyright 2011-2013 apps.ownCloud.com Team  
All rights reserved. apps.ownCloud.com is not liable for any content or goods on this site.
All contributors are responsible for the lawfulness of their uploads.