playSMS 1.4.7 test version

Hi,

Would like to invite you to tests this version before released as 1.4.7:

Changes:

  • Simplify db query for faster page load on Reports
  • Better search form on Reports
  • Provides sql file for applying db table indexes
  • Remove dependency to PEAR/DB, now use PDO for db operations
  • Compatibility up to PHP 8 (should be up to 8.2)
  • Fix some bugs and security related

Please examine full change logs:

Or for those who have been following, change logs with previous tag:

I hope this version will not introduce new bug or new vulnerability, when you find one, please visit playSMS security policy page:

Thank you,
anton

Installed playsms-1.4.7 test version
Ubuntu 22.0.4
PHP 8.2.12
Apache2

Under Manage Accounts, when doing Administrator, User or sub-user search will return MySQL error
FATAL ERROR : Database query execution has failed

Hi,

A fix has been committed and pushed:

Please replace plugin/core/dba/fn.php with this version:

anton

Thanks Anton. It FIXED after the patch.

Compose Message can’t enter mobile number of receipient.
Got circling icon at the end of box. When press enter, field is cleared (no number)

Hmm that one should be fixed already, but let me double check on my test installation. Or maybe try to use comma , instead of Enter.

If you notice issue on visiting phonebook page, that is also being fixed, by copying from 1.5.0-beta8.

anton

Or maybe try to use comma,instead ofEnter .
Ok that works if use ‘,’ (comma) after key in the phone number

Hi,

The compose message bug is fixed, download new file here:

Replace plugin/feature/phonebook/phonebook.php

anton

  1. Entering phone no in compose message need to enter comma after keying in mobile number
  2. Seems the Group Icon and Add a use in phonebook is missing. Only import and export icon available

Screenshot 2023-11-22 at 11.44.28 AM

Hi,

Fixes committed and pushed, please check the latest phonebook:

You need to download all phonebook’s php files and use them to replace.

anton

Hi

  1. Phonebook OK
  2. Entering new number in compose message still need use comma. Can’t use ENTER after entering number. (previous version can use Enter and comma for entering new number)

Thanks

Hi,

So, its like this:

  • Suppose I have a phonebook entry: 15550001 and 15550002
  • When I enter 15 up to 1555 or up to 1550000 all good
  • But when I enter 15557, it wont find any entries on phonebook, then you cannot select anything, and the only way to force it is by using comma
  • Enter is for selecting whats available options the results of phonebook lookup

anton

Hi

  1. Ok noted on the explaination BUT I was comparing with previous version 1.4.6 it was working to use ENTER when entering NEW number (not found in the phonebook)

Thanks

Understood, I kinda remember this issue, I’ll try to fix it

Please have more tests, especially comparing with 1.4.6, thanks

I want to stop working on 1.4.x series and leave it with relatively minor bugs and some minor inconveniences, but still a working app. I’ll be focusing the dev on 1.5 series, for better themes, reporting pages, faster bulk sending and delivery reports etc, if possible that is and if my time/resources allowed

anton

1 Like

Hi,

Message Template edits open back based template good Morning NOT the actual template to be edited.

Thanks

Fixed:

dba_valid() now returns true or false, not the actual value like it used to

anton

Hi,

Now its working like previous, please re-update the phonebook.php

anton

Hi
Thanks. It FIXED the message template issue.

Hi Anton,
Here are some of the issues that I found out

Normal User

  1. Settngs
    1. Manage site - returns error 500 page
    2. Manage subuser - returns > FATAL ERROR : Database query execution has failed
    3. Manage credit - returns > FATAL ERROR : Database query execution has failed
  2. Report
    1. My credit transactions returns > FATAL ERROR : Database query execution has failed

Admin User

  1. Settings
    1. Manage firewall. returns > FATAL ERROR : Database query execution has failed
    2. Manage stoplist returns > FATAL ERROR : Database query execution has failed
    3. Manage subuser - returns > FATAL ERROR : Database query execution has failed
  2. Report
    1. My credit transactions returns > FATAL ERROR : Database query execution has failed

Hi,

Those, and manage sender id, should be fixed now.

Tagged here:

anton