I see the php-iworx package, which I think is intended for NodeWorx/SiteWorx usage only. However, when I access phpMyAdmin through SiteWorx, it stays on the Iworx PHP server and I see this message:
The mbstring PHP extension was not found and you seem to be using a multibyte charset. Without the mbstring extension phpMyAdmin is unable to split strings correctly and it may result in unexpected results.
Sounds dangerous. :eek:
I have the php-mbstring package installed for Apache. Should there be a php-iworx-mbstring package, too? I am fairly certain I started seeing this message after the upgrade to v2.0.
mbstring is part of php iworx.
Here is the list of all php rpms relating
-103. is mine own rebuild, you should have 100.
So you may find these RPMS in http://updates.interworx.info
Try to simply do
yum install php-mbstring
But it should be better to open a support ticket
Odd, neither of my boxes had at rpm installed and I have used PHPMyAdmin with no problems. In any event both have it now.
The message is harmless for most operations. We’ll be including mbstring in a future php-iworx release to quell any issues.
does I do not understand well ?
Chris, he may simply do a yum install php-mbstring ? ins’t it ?
No, remember, iworx-cp uses its own PHP, and since phpMyAdmin is being accessed via iworx-cp’s PHP then php-iworx is what will get mbstring. The php-mbstring package affects the system php and not iworx-cp’s.
Great! Some databases we work with use Unicode, so I’ll be looking for it. And I’ll take your word for it that most operations work fine despite the warning. But can you tell me what phpMyAdmin features I should definately avoid in the mean time?
If you’re using unicode then you may be affected. I’m assuming the probs would occur on UPDATES and/or INSERTS. Queries, since they are read-only, I assume would work ok (or at least not mess up any data).