|
|
How is your Nextcloud installed ? Are you using the Nextcloud AIO (All-in-One) Docker image ? |
|
|
I'm running it in an Ubuntu VM. I originally installed manually via the zip file. I had attached some screenshots, but I don't see them here. Are they hidden or did they fail to upload? |
|
|
I'm not very good at this... but maybe this will be helpful. I've tried to debug the javascript that's creating that text. This is as far as I've gotten. In adminsettings.js, line 318, that function key is getting set to 'toRgb', so the usrval is getting set to the output of the toRgb function, which is that depreciation warning. Again, I'm not very good at Javascript debugging of complicated projects, but hopefully this is helpful. Screenshot_20240213_211938.png (50,299 bytes) |
|
|
The lists of available users and groups are working fine on our server, without any errors. The code that you show in the screenshot from above has nothing exotic in it. It just collects the users from the 'allUsers' variable and adds some html tags around them to create the drop-down list. The problem is that in your setup, the 'allUsers' variable comes with some weird content in it. Since, as you mention, in the restricted numbers section, the groups are shown correctly, and the JavaScript code for groups is identical with that for users, as can be seen above, it follows that the code for users is fine, but the content that comes from the database and is stored in the 'allUsers' variable, is not fine. This can have multiple causes, including using an incomplete or outdated PHP or MariaDB installation. 1. Have you created multiple users, both admins and non-admins, in your Nextcloud ? Do their names contain characters such as dots, dollar signs, etc. ? Have you created multiple groups apart from the 'admin' group in your Nextcloud and assigned users to groups ? Do the group names contain special characters ? 2. What errors do you see in the Nextcloud log (Administration Settings > under Administration > click Logging) ? The error that you posted is generated by some Nextcloud file and is out of place, since it mentions "String.prototype.toRgb is deprecated! It will be removed in Nextcloud 22.", but it shows up in Nextcloud 28. When you click on the users/groups buttons to see the list with all users/groups, do you see any errors in your browser's console (not in the pop-ups) ? 3. Since you mention that you installed Nextcloud manually, from the zip archive downloaded from the Nextcloud website, we deduce that you are using Apache, instead of Nginx. Please confirm that you installed Nextcloud on a subdomain and not on a subdirectory and that you configured Apache as explained here: https://www.doublebastion.com/apache-configuration-for-nextcloud/ , especially the part about enabling pretty URLs and updating the '.htaccess' file. 4. Please confirm that you run the latest version of Nextcloud (28), the latest version of SMS Relentless (1.3.2), on an Ubuntu server with the latest version of PHP and MariaDB. 5. Please provide the URL of the admin settings page of the app. Replace your real domain and subdomain with 'cloud.example.com' for privacy reasons, like this: https://cloud.example.com/settings/admin/sms_relentless |
|
|
> Have you created multiple users, both admins and non-admins, in your Nextcloud? Yes. One admin and one standard user. > Do their names contain characters such as dots, dollar signs, etc. ? Yes. The standard user is firstname.lastname. > Have you created multiple groups apart from the 'admin' group in your Nextcloud and assigned users to groups ? No. There is only the Admin group. > Do the group names contain special characters ? No. > What errors do you see in the Nextcloud log (Administration Settings > under Administration > click Logging) ? The only error I see is this: "Error \t PHP \t Trying to access array offset on value of type bool at /var/www/cloud.mydomain.foo/apps/sms_relentless/lib/Service/SmsrelentlessService.php#3418" > When you click on the users/groups buttons to see the list with all users/groups, do you see any errors in your browser's console (not in the pop-ups) ? I've enabled debugging so that I can see them. I've attached a txt file with the console log. > we deduce that you are using Apache True > Please confirm that you installed Nextcloud on a subdomain and not on a subdirectory It is installed as cloud.mydomain.foo, no subdirectory. > and that you configured Apache as explained here: https://www.doublebastion.com/apache-configuration-for-nextcloud/ , especially the part about enabling pretty URLs and updating the '.htaccess' file. Yes. This is done. > Please confirm that you run the latest version of Nextcloud (28), the latest version of SMS Relentless (1.3.2) Yes. Nextcloud 28, SMS Relentless 1.3.2. > on an Ubuntu server with the latest version of PHP and MariaDB # dpkg -l php8.2 mariadb-server | grep ^ii ii mariadb-server 1:10.3.39-0ubuntu0.20.04.2 all MariaDB database server (metapackage depending on the latest version) ii php8.2 8.2.15-1+ubuntu20.04.1+deb.sury.org+1 all server-side, HTML-embedded scripting language (metapackage) > Please provide the URL of the admin settings page of the app. https://cloud.mydomain.foo/settings/admin/sms_relentless js-console.log (3,864 bytes) Screenshot_20240214_105727.png (21,101 bytes) |
|
|
Oh, I should mention... I'm not using php-fpm. I'm using mod_php. libapache2-mod-php8.2 8.2.15-1+ubuntu20.04.1+deb.sury.org+1 |
|
|
Everything that you posted looks ok. The warning "The global jQuery is deprecated" can be ignored. The only problem we see with your installation is that your users contain dots in their names, which can cause problems in JavaScript, since dots are used to access object properties. You can replace the dots with hyphens (-) or underscores (_) in your usernames and Display Names where it appears. Also, you can create at least one group. You don't need to assign users to that group. All can be done on the 'Users' page of Nextcloud. Then post if you can see the list of users and groups when clicking on the respective buttons. You can use Fireforex, after removing all the cached data. |
|
|
Well... I think that's it. I added a user 'TestUser' and now that's the only user that shows up. I also added a group 'TestGroup' and that shows up as well. I'm setting this up, not only for myself, but also as a testing for work. We have about 30 users, all firstname.lastname in LDAP. Is it possible to make this work with dots in the user name? Screenshot_20240214_133019.png (7,609 bytes) |
|
|
In principle, it should be possible if we escape the dots in usernames and Display Names, but we have to test it before implementing it in the next app version. Just to be clear, in the example from above "TestUser" is the "Display Name" of the user, and not his "username", which can be different (like "user_153") and is used to log in to Nextcloud. When you mention you have 30 users with "firstname.lastname", you are referring to the 'usernames' that they use to log in to Nextcloud, or to their "Display Names" that in general are different and are shown in the allowed users pop-ups of SMS Relentless ? |
|
|
I spoke a bit too soon. I'm not sure if this is related, but I can't save the access restrictions because the 'Restriction Author' is set to 'Null' for some reason. The error in the log is: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'saved_by_dsplname' cannot be null"}} I've tried setting the value of the html form input element with developer tools, just as work around and to gain more insight into the issue, but have not had success. Screenshot_20240214_135637.png (67,428 bytes) |
|
|
The user names are the login names, not the display names. The non-admin I have that doesn't show up only has a dot in the login name. The display name is "Firstname Lastname". The login name is "firstname.lastname". The one that works is "TestUser" for both. |
|
|
If your own Display Name as admin, contains a dot, this can cause the problem when trying to save the restrictions. Also, if you don't have a Display Name set up. Please confirm that you have both a username and a Display Name on the Users page of Nextcloud, and that both your username and Display Name don't contain a dot or other special character. |
|
|
I do. the 'cloudadmin' user did not have a separate display name, so it was just showing 'cloudadmin'. Now it's set to 'CloudAdminDsp'. I opened up a private window to test, and it's doing the same thing. The 'Restriction Author' field is 'null'. I'm going to play around with it and see if I can figure anything out. |
|
|
If you can open the "/var/www/cloud.mydomain.foo/apps/sms_relentless/js/adminsettings.js" file and search for this line: $('[id^="rstsave-"]').click(function(event) { you can add right below it the following line: alert("The Display Name of the current admin who tries to save the restrictions is: "+ crntadmDispName); to see if your Display Name as an admin is correctly retrieved from the database. Then click on the Save button on the row of the restriction, to see what the alert shows. |
|
|
When you click on the plus sign in the "Restrict access to the following phone numbers" section, to add a new restriction, what is the value included automatically in the 'Restriction Author' field ? Is it "null" ? |
|
|
I created a new user 'testadmin'/'TestAdminDsp' and added them to the admin group. I can use this user to change the access restrictions. I don't know why it doesn't work with 'cloudadmin'. They're set up the same, and look the same in the database. |
|
|
Sorry I didn't see your reply. I'll run that test now. |
|
|
Yes, it says 'null'. But if I use my new admin account, it works. I don't know what the difference is between the accounts. I can't find any. |
|
|
Here are some screenshots and sql data. Screenshot_20240214_151604.png (14,266 bytes) Screenshot_20240214_151631.png (14,790 bytes) |
|
|
Can you save a Display Name for your 'cloudadmin' user in Personal Settings > Personal info > Full name, then log out, clear browser cache, log in again as 'cloudadmin' and see if you can save a new restriction ? |
|
|
The app tries to obtain the 'Display Name' for 'cloudadmin' from the table 'oc_accounts_data' of your Nextcloud installation. So, if you inspect your Nextcloud database and look into the 'oc_accounts_data' table and you see: cloudadmin displayname [empty space] it means this is the cause of the problem. |
|
|
Oh my..... The 'cloudadmin' and 'benjamin.long' users are completely missing from this table. I think we found the root of the issue. Maybe the dot was never a problem? |
|
|
I logged into the missing users, disabled and re-enabled the profile, and that populated the oc_accounts_data table. Now it all works, including the user with the dot. This has been an interesting journey. Thank you so much for your time! Now I can move on to the rest of the testing. |
|
|
So, now, even a user with a dot in the username is listed in the allowed users pop-up ? And no other errors ? |
|
|
Yes, it's all working. I've received and send texts from my firstname.lastname account. I was able to restrict this account to just one of the numbers on the account. I'm not seeing any errors. Now I'm trying to figure out the best way to use it from a smartphone. I was hoping the nextcloud android app would have some functionality, but it doesn't seem to. I do get the notification though. Thanks again for your help! |
|
|
You are welcome. We'll mark this issue as solved. However, we will be releasing a new version of SMS Relentless in a few hours, to solve a small bug and add new features like automatically refreshing the 'Received Messages' table when receiving a new SMS. It would be ideal if you could upgrade to the latest version before other tests. We'll post here when the new version will be published, in a few hours. |
|
|
Will do! |
|
|
Version 1.3.3 of SMS Relentless has been published. If you have any issues with the new version, please don't hesitate to open a new thread here, or on GitHub (https://github.com/DoubleBastionAdmin/sms-relentless/issues). You can also send any questions or suggestions directly to tech at doublebastion.com. Thank you. |
|
|
Hello, We published a new version of SMS Relentless which was optimized to work on mobile phones. It also introduces the 'Conversations' page ( image 1_ ). If you are still interested to use the app on mobile phones, the easiest way is to install Firefox for mobile (version 123.0 or newer), then verify that 'Ask to save' is set in Firefox's 'Settings' > 'Logins and passwords' > 'Save logins and passwords' ( image 2_ ). Then access your Nextcloud login page in Firefox and after you enter your username and password, when you are asked if you want Firefox to remember your login, answer Yes. After you've logged in to Nextcloud, open the main Firefox menu (from the low right-hand corner) and choose 'Install' ( image 3_ ), to create a shortcut for Nextcloud on your mobile's screen. This shortcut will look like any mobile app ( image 4_ ). In this way, each time you want to access Nextcloud and its applications, including SMS Relentless, you just press the 'Nextcloud' shortcut, choose the proposed login credentials which are stored safely by Firefox (to avoid writing again your username and password) and then you are in Nextcloud, which has a responsive design. At least its main functions and SMS Relentless can be used on mobile phones. We are not referring here to using the official Nextcloud app for Android or iPhone. That is an entirely different setup and it doesn't allow using the apps installed inside Nextcloud, like SMS Relentless. So, once you are logged in to Nextcloud using Firefox for mobile, you can access SMS Relentless like on a desktop computer, and use all its functions, including listing all the received messages ( image 6_ ) or using the reply pop-up window ( image_7 ) to send a quick reply. 1_active_archived_conversations.png (312,570 bytes) 2_save_login_and_password.png (195,366 bytes) 3_add_nextcloud_shortcut_to_home_screen.png.png (98,440 bytes) 4_firefox_and_nextcloud_shortcut.png (625,203 bytes) 5_sms_relentless_on_mobile.png (136,641 bytes) 6_received_messages_on_mobile.png (154,832 bytes) 7_reply_to_message_on_mobile.png (153,880 bytes) |
- Anonymous
