Answers

• allan Posts: 61,972Questions: 1Answers: 10,160 Site admin

  March 21

  You might need to do:

  $db->sql('set names utf8');
  

  before using the Editor::inst() constructor. It really depends on the PHP and MySQL setup if it is needed or not.

  Allan
• pisisler Posts: 113Questions: 23Answers: 1

  March 21

  Thanks Allan. You might miss that I already said I did that in ssp.class.php and it worked. I just wonder why I needed this while especially I already have the charset in connection string. As for the Editor, it is just working fine. Only DT instance is breaking the encoding. I find it interesting that;

  1- My PHP and server settings didn't change. I just updated DT files. Why would the encoding change all of a sudden?

  2- My production site has a page with DT and has another page with DT + Editor. How come DT + Editor works fine but the other page which has only DT is used broken. It is actually a single project which uses the same files to display the tables in different pages.
• allan Posts: 61,972Questions: 1Answers: 10,160 Site admin

  March 22

  I was a bit confused about the ssp.class.php part. The first part of your post suggests that you are using Editor? You typically wouldn't use the ssp.class.php file as well as Editor's PHP libraries, since they provide far more flexibility than the limited demo of the ssp.class.php file.

  1- My PHP and server settings didn't change. I just updated DT files. Why would the encoding change all of a sudden?

  Without being able to debug the server, I don't I'm afraid. I guess something in the database connection setup I use changed, but I don't recall what that would be.

  2- My production site has a page with DT and has another page with DT + Editor. How come DT + Editor works fine but the other page which has only DT is used broken

  I also don't know that without being able to debug it. Sorry.

  If you need set names utf8, then that's fine - some database connections do need that. You could call it in ssp.class.php and after the Editor PHP libraries have been included (although again, I don't understand why both would be used).

  Allan
• pisisler Posts: 113Questions: 23Answers: 1

  March 23 edited March 23

  I don't understand why both would be used

  Sorry if I couldn't make it more clear. It is because:

  2- My production site has a page with DT and has another page with DT + Editor.

  In my application, I have a page which lists the company's products, a page which allows editing the product information. This page obviously loads both DataTables and Editor (but doesn't use ssp.class of course). And the application has also a page for displaying the application logs, which obviously doesn't need editor and it uses just DataTables. (Here comes in ssp.class)

  The products page, without running any set names utf8 command displays the UTF8 chars correctly, whereas the very same database and the same server breaks the very same chars when loaded in logs page with spp.class.
• allan Posts: 61,972Questions: 1Answers: 10,160 Site admin

  March 24

  which obviously doesn't need editor and it uses just DataTables. (Here comes in ssp.class)

  Ah! I'd just use the Editor class, but add a call to ->write(false) - see this post. Means less code to maintain .

  There must be some kind of interaction from the charset that is causing the difference. That's the only thing I can think of that is different really.

  Allan
• pisisler Posts: 113Questions: 23Answers: 1

  March 25

  Sounds quite better, I will give it a shot. But as far as I can tell, client-side JS files to be loaded is still the same as with ssp.class right?
• allan Posts: 61,972Questions: 1Answers: 10,160 Site admin

  March 25

  But as far as I can tell, client-side JS files to be loaded is still the same as with ssp.class right?

  Correct

  Allan