Seems that latest jQuery 3 code in DokuWiki broke fullcalendar, on which davcal is based. Probably, an update of fullCalendar can fix this.

Yeah, mine looks similar to yours. You can try to style the calendar output by modifying fullcalendar-2.4.0/fullcalendar.print.less (it's a standard CSS stylesheet).

I have uploaded calendar printed from browser (dokuwiki.pdf), and for reference a very nicely formatted calender printed from osmo organizer (osmo.pdf). Google calender has more or less also similarly nice export / print to pdf.

Yes, please upload a screenshot of the differences. I just tried printing (Firefox 49.0.1) and IMHO it looks very nice! Day/Week view are more condensed in print, but that could be by design (fullcalendar's unmodified print stylesheet is applied).

Hi,
printing is indeed currently possible from the browser, but the output is quite ugly. I had in mind adding nicely formatted calendar output/export functionality. If it is not exactly clear what I mean, I can attach, or send you two sample outputs (one current, and one desired for comparison)

Thanks for your comment.

A basic editor for events created within DokuWiki doesn't seem too difficult. However, making it compatible with events created and/or modified by other clients is the hard job.

Thanks for testing, I'll add it to the next release.
Did you also test password changing?

Hey there! sorry the long time away and answer
how ever! it works perfectly !
thanks

Could you please test if the latest development version works for you? Here is the direct link: https://www.aboehler.at/hg/user_sql/archive/e6a991d13870.tar.gz

I used postfix admin to set password and I think it uses 'doveadm pw -s CRAM-MD5 -p $password'
and yes the strings in my database is cram-md5

Hm, my initial though was that it is impossible due to the way CRAM-MD5 works. However, it seems that someone wrote a library recently: https://github.com/hn/dovecot-misc/blob/master/dovecot_hmacmd5.php

Obviously, you do not have the PDO mySQL driver installed. That's a problem of your NAS, nothing I can do about.

it's on freenas jail

If you read through the documentation, you will find the option "timezone" which should solve your problem.

Yes, now it works

OK, user_sql has just been released to the Nextcloud app store. Plus, I changed the way archive folders are created, so now it should also work with the release on OwnCloud's app store.

This issue includes a fix to the code and does not only involve disabling the app code checker.

I have tried your suggestion,

I'm sorry, NC10 is, of course, supported and it works fine for me. However, I have not yet upgraded to 10.0.1, which you are probably running.

I never tried it with NC10, as soon as I upgrade, this problem will be fixed.

This would be a nice Admin Plugin...

you're welcome, I'm closing this...

hey, so you were right . when I set the field "User active" to "Block" and "Invert active values" , it works now. Thank you.

By the way: If you go through the Joomla docs you'll notice that the column "activation" is meant for a completely different thing: It controls whether activation emails are to be sent!
You want the column "block" and, of course, need to check the "invert active value" box.

I went over your screenshot of the app configuration again and I think I found your problem: You must activate "Invert Active Value" (I did not bother entering the table for "User Active Column" in the first place)

But my MySql Server ist configured by Plesk. Maybe here are another settings adjusted.

I did not change the configuration of the sql server. I just created a new local user and selcted "Create database with same name and grant all permissions" in phpMyAdmin.

okay, that's strange. maybe its a misconfiguration of my mysql server? can you give me the config of your mysql server? so I can compare it

I just did a fresh installation of Debian Jessie, ownCloud 9.1.0, user_sql 2.3 and Joomla 3.6.2. Everything went without problems, my Joomla user is in the list and is able to login.

Okay, Thanks for your time!

That's really strange. The log doesn't even include information about ownCloud trying to list the users from the user_sql backend.

Yes this is only the one server. i have duplicate the login information's to "default" and now without errors, but its no synchronizing (i cant see the Users of the another Database)

Hm, looks quite fine to me.
Is this the only domain you serve ownCloud on? If yes, what happens if you duplicate your settings for domain "default"?

Hi Andreas, yes i click on "Save" after Verify Settings :)

It seems that either saving or loading of the settings fails (you did click on "Save", right?).
Could you give some more info, please:

i have now noticed that the users got copied from the external sql database to the oc_users table (probably by some broken owncloud upgrade in the past). the principal admin acount never was on user_sql and could always log in. with this admin account in "users" i activated "show user backend" — all relevant accounts had "database" written there, instead of SQL.

Thanks for the logs. Could you try clearing your browser cache and cookies and logging in again? Did you check from a different computer?

i'm not running any extra authentication plugins. the i'm using postgresql as the database backend.

That's strange, I'm running on NextCloud 9 for quite some time now (actually, since its release).
I tested it on ownCloud 9.1 just yesterday and I did not notice any problems.

OK, I found the problem: It's the PHP7 update and an incompatibility with the version of Sabre/DAV I'm using for davcal. See the problem for ownCloud, I applied their patch: https://github.com/owncloudarchive/calendar/issues/1002

I'm currently testing a few things, it seems that OutlookCalDavSynchronizer requests only events within a certain time span. davcal does not report any events back, so it looks like a problem somewhere within davcal.

Your link is correct.

Did you use this one: https://sourceforge.net/projects/outlookcaldavsynchronizer/?

It seems that the previous commit accidentally broke the creation of new events by not defining a necessary variable in the client side JavaScript.