Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

No longer in NextCloud store after NextCloud 15 update #18

Closed
csharpner opened this issue Jan 3, 2019 · 19 comments
Closed

No longer in NextCloud store after NextCloud 15 update #18

csharpner opened this issue Jan 3, 2019 · 19 comments

Comments

@csharpner
Copy link

After the update to NextCloud 15, this app no longer shows in the NextCloud app store. I do see it's still on the public website here: https://apps.nextcloud.com/apps/quicknotes
but it's no longer available in the apps to choose from with my admin account on my locally installed instance.
@ntinti
Copy link

ntinti commented Jan 10, 2019

Maybe it does not work with 15?

@daniu-de
Copy link

I just tried - yes: quicknotes is currently not compatible with Nextcloud 15.

Even adjusting the max version in /appinfo/info.xml does not help (you can activate the app but it is not usable.

Something needs to be done

@toms1342
Copy link

Please update this beautiful app!
We are having so much fun using it.

@Leorivasc
Copy link

Please, please, please! the app is amazing and I had a lot of notes there!!

@matiasdelellis
Copy link
Owner

😞
Sorry for the inconvenience!. 😢 😭

I still do not have an instance with NC 15, but soon I will solve it!

@Githopp192
Copy link

Hi matiasdelellis .. i can support you on this .. :-)
I've got much experiences building NC Instances VM based like VirtualBox, VmWare and more.
Just get in contact with me .. and we should quickly be able to build a Nextcloud 15 virtual environment

(i did fully automate this once on Centos based Installation) ..

You may know .. Users working in a Cloud .. they do not feel much comfortable, when the created data in a cloud .. and they are not finding them anymore after a NC Upgrade .. :-)

matiasdelellis added a commit that referenced this issue Feb 12, 2019
@matiasdelellis
Move to precompiled handlebars templates.
6bac240 
In Nextcloud 15 the default Content Security Policy disallows unsafe
eval expressions, so Handlebars templates can no longer be compiled at
runtime.

Fix issue #18
@matiasdelellis matiasdelellis mentioned this issue Feb 12, 2019
Merged
@matiasdelellis
Copy link
Owner

Hi @csharpner @ntinti @daniu-de @toms1342 @Leorivasc @Githopp192

Please try the last PR 😃

@matiasdelellis
Copy link
Owner

Hi matiasdelellis .. i can support you on this .. :-)
I've got much experiences building NC Instances VM based like VirtualBox, VmWare and more.
Just get in contact with me .. and we should quickly be able to build a Nextcloud 15 virtual environment

(i did fully automate this once on Centos based Installation) ..

I have to do this at some point.. 😞

You may know .. Users working in a Cloud .. they do not feel much comfortable, when the created data in a cloud .. and they are not finding them anymore after a NC Upgrade .. :-)

Just a tip. if you work professionally selling services, never use the latest stable version. Stay in the production version. 😉
I am just an example, is impossible to continue maintaining all the versions..
It is tempting to use NC15 for all the new features, but they themselves do not recommend using it in professional enviroments.. 😅

@Githopp192
Copy link

Githopp192 commented Feb 12, 2019 •
edited
Loading

Hm .. then i have to open a new Nextcloud/server case .. because, exactly about the reason you are mentioning .. i'm using the Channel "updater.release.channel": "production" ! .. so i got a reminder that a new Version is there, NC Version 14.0.7 (was on 14.0.6) .. so i triggered the NC-Update from CLI .. and NC did recommend the Version 15.04 (i did NOT change the Channel) .. so what went wrong here .. ?

By the way ... what you're saying .. i can fully understand :-) .. and my suggestion to support you (NC Virtualization is still intact :-) ) ...

@Githopp192
Copy link

just opened a NC-Server case .. you see .. i was on the Production Channel:

Nextcloud Updater - version: v14.0.2RC2-1-g21ab216

Current version is 14.0.6.

Update to Nextcloud 15.0.4 available. (channel: "production")
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-15.0.4.zip

@Leorivasc
Copy link

Yeah, I was also on 14, but in 'stable' channel, but was also upgraded to 15
☹

@matiasdelellis
Copy link
Owner

MM.. WIth Stable, it's okay to upgrade to NC15.. Always update to the last stable ..
In 'Production', the major updates are delayed, until NC people considered suitable for professional environments.

The problem is that it is not well defined when it is considered suitable for production. 😞
Before it was well documented, but now I can not find which is the stable version and which is the production one. 😥

This is very important, but please ask to yo to test the last pull-request.. 😅

@Leorivasc
Copy link

yeah, only had to read: "stable is the most recent stable version. It is suited for regular use and will always update to the latest major version" 🤦‍♂️

@rob006
Copy link

rob006 commented Feb 12, 2019

In admin panel production channel is described as:

production will always provide the latest patch level, but not update to the next major release immediately. That update usually happens with the second minor release (x.0.2).

Last release is 15.0.4. Stable 15.0.0 was released two months ago and 15.0.2 a month ago.

@Githopp192
Copy link

yes .. thx rob006, that's i was remembering, too ..
Upon this, this was my expectation .. landing from 14.0.6 to 14.0.7 (as previously suggested from NC) .. or landing on NC 15.0.2 .. but not 15.0.4 :-( .. anyway .. i did open a NC Server case .. because this - i think - is very important for many users about Stability and the NC Enterprise Services

@Githopp192
Copy link

to keep you posted (regarding the other case, i have open about .. )

Upon the official Nextcloud Documentation -->

"We start the incremental rollout to the Production channel after the first bugfix release (for example, 12.0.1). Packages for the Release channels might be available in distributions, this is up to the packagers.

To upgrade in the safest way possible, always update to the latest minor release before upgrading to a new version. As an extreme example, to upgrade from 9 all the way to 12.0.5, upgrade 9.0.x to 9.0.6, then upgrade to 10.0.6, 11.0.7, then 12.0.5."

So when i wish to stay on the Production Channel as long as possible (regarding the official message from Nextcloud "To upgrade in the safest way possible, always update to the latest minor release before upgrading to a new version"), then i had to upgrade from 14.0.6 to 14.0.7, after that to 14.0.8.

Doing so .... i think i had to manually initiate the Upgrade (because NC already suggested the Major Upgrade,which would be the automatic way..).

Or is there a possiblity to manually choose the Version to be upgraded, which could trigger an automated Upgrade, too ?
i.e. in my case .. /bin/php /var/www/html/nextcloud/updater/updater.phar 14.0.7 ??

@matiasdelellis
Copy link
Owner

Well .. Obviously they already decided that NC15 is stable enough, and I do not think they will do anything about it. 😅

I dont know.. 🤷‍♂️
But publish a new version and it should work on both NC14 and 15.. 😅
With some additions ... 😉

Please. Check it..

@Leorivasc
Copy link

I guess the gap between versions was unfortunately too short to react on time, I mean, jumping from 14.0.8 to 15?, I would say v14 was far too short lived. Hope v15 at least lives to see 15.1.

@matiasdelellis
Copy link
Owner

Well,
NC 12.0.0 May 22 2017
NC 13.0.0 February 6 2018
NC 14.0.0 September 10, 2018
NC 15.0.0 December 10, 2018

12 to 13: 9 Months
13 to 14: 7 months
14 to 15: 3 months.

Obviously, they are decreasing the time between versions.. 😞

@Githopp192 Githopp192 mentioned this issue Feb 13, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@matiasdelellis @rob006 @ntinti @daniu-de @csharpner @toms1342 @Githopp192 @Leorivasc