Feedback to: Textpattern CMS 4.6.0 beta 2 released

bici · 2016-08-03 22:14:15

johnstephens wrote #300492:

Another question: A fresh install with 4.6 sets dbcharset in the config.php file to utf8mb4. Is that something we should update when upgrading an existing site to the new version?

good question. what is the best setting? i have $txpcfg[‘dbcharset’] = ‘utf8’;

phiw13 · 2016-08-03 23:06:36

johnstephens wrote #300492:

Another question: A fresh install with 4.6 sets dbcharset in the config.php file to utf8mb4. Is that something we should update when upgrading an existing site to the new version?

I don’t think so. If your existing site is running fine (with UTF8), there is no reason to change. As far as I understand it, utf8mb4 is an extension (a superset) of UTF8.

mrdale · 2016-08-03 23:24:53

Longtime irk that I’d love to see changed… the “with selected”.

I think it should be above the articles.
I think there is clearer wording like “actions” or “work on checked” or “work on selected | selection”

On sites with a lot of content and a long listing where you want to work on a long list of selectionsTXP currently forces you to scroll to the end of the page.

I like this one much better…

phiw13 · 2016-08-03 23:33:47

mrdale wrote #300495:

Longtime irk that I’d love to see changed… the “with selected”.

I think it should be above the articles.

Depends on your work flow… I typically scroll down the list and check one or more items. By the time I’m ready to take action, I’m actually at or near the bottom of the listing.

mrdale · 2016-08-04 00:18:12

phiw13 wrote #300496:

Depends on your work flow… I typically scroll down the list and check one or more items. By the time I’m ready to take action, I’m actually at or near the bottom of the listing.

I see it more the other way on my travels around the web, but your mileage may vary.

gaekwad · 2016-08-04 13:46:53

phiw13 wrote #300494:

I don’t think so. If your existing site is running fine (with UTF8), there is no reason to change. As far as I understand it, utf8mb4 is an extension (a superset) of UTF8.

That’s also my understanding. utf8mb4 is backwards-compatible with utf8, but extends support to emoji and other typographical horrors.

gaekwad · 2016-08-04 13:49:42

philwareham wrote #300490:

Just a note that there will be another beta at least before the final release,

I’ll prepare the demo site for beta 3.

ruud · 2016-08-05 17:59:37

johnstephens wrote #300492:

Another question: A fresh install with 4.6 sets dbcharset in the config.php file to utf8mb4. Is that something we should update when upgrading an existing site to the new version?

You can’t just simply change the charset in the config file. The tables in the database need to be updated as well to reflect this change.

ruud · 2016-08-05 18:02:12

johnstephens wrote #300489:

Question: How can I compare the trace summaries for 4.5.7 and 4.6? 4.6 provides units, and 4.5.7 doesn’t:

Runtime and query time in 4.5.7 was in seconds. Multiply by 1000 to get the time in milliseconds.

johnstephens · 2016-08-05 18:02:14

ruud wrote #300508:

You can’t just simply change the charset in the config file. The tables in the database need to be updated as well to reflect this change.

Thank you, Ruud! That was my hunch. But I thought tables were created during installation, right? Why would the config file need a persistent reminder of this? For plugins that create tables? Something else?

johnstephens · 2016-08-05 18:02:56

ruud wrote #300509:

Runtime and query time in 4.5.7 was in seconds. Multiply by 1000 to get the time in milliseconds.

Thank you!

ruud · 2016-08-05 18:04:36

johnstephens wrote #300510:

Thank you, Ruud! That was my hunch. But I thought tables were created during installation, right? Why would the config file need a persistent reminder of this? For plugins that create tables? Something else?

Otherwise you’d have to query the database first to find out the charset (assuming that is possible), so this saves a query per page request.

johnstephens · 2016-08-05 18:05:25

ruud wrote #300512:

Otherwise you’d have to query the database first to find out the charset (assuming that is possible), so this saves a query per page request.

Awesome, that makes sense!

philwareham · 2016-08-06 07:44:06

I am investigating ways to bring the tag builder back into 4.6.0.

miles · 2016-08-06 09:17:58

philwareham wrote #300517:

I am investigating ways to bring the tag builder back into 4.6.0.

Thank you!

Textpattern CMS support forum

#31 2016-08-03 22:14:15

Re: Feedback to: Textpattern CMS 4.6.0 beta 2 released

johnstephens wrote #300492:

#32 2016-08-03 23:06:36

Re: Feedback to: Textpattern CMS 4.6.0 beta 2 released

johnstephens wrote #300492:

#33 2016-08-03 23:24:53

Re: Feedback to: Textpattern CMS 4.6.0 beta 2 released

#34 2016-08-03 23:33:47

Re: Feedback to: Textpattern CMS 4.6.0 beta 2 released

mrdale wrote #300495:

#35 2016-08-04 00:18:12

Re: Feedback to: Textpattern CMS 4.6.0 beta 2 released

phiw13 wrote #300496:

#36 2016-08-04 13:46:53

Re: Feedback to: Textpattern CMS 4.6.0 beta 2 released

phiw13 wrote #300494:

#37 2016-08-04 13:49:42

Re: Feedback to: Textpattern CMS 4.6.0 beta 2 released

philwareham wrote #300490:

#38 2016-08-05 17:59:37

Re: Feedback to: Textpattern CMS 4.6.0 beta 2 released

johnstephens wrote #300492:

#39 2016-08-05 18:02:12

Re: Feedback to: Textpattern CMS 4.6.0 beta 2 released

johnstephens wrote #300489:

#40 2016-08-05 18:02:14

Re: Feedback to: Textpattern CMS 4.6.0 beta 2 released

ruud wrote #300508:

#41 2016-08-05 18:02:56

Re: Feedback to: Textpattern CMS 4.6.0 beta 2 released

ruud wrote #300509:

#42 2016-08-05 18:04:36

Re: Feedback to: Textpattern CMS 4.6.0 beta 2 released

johnstephens wrote #300510:

#43 2016-08-05 18:05:25

Re: Feedback to: Textpattern CMS 4.6.0 beta 2 released

ruud wrote #300512:

#44 2016-08-06 07:44:06

Re: Feedback to: Textpattern CMS 4.6.0 beta 2 released

#45 2016-08-06 09:17:58

Re: Feedback to: Textpattern CMS 4.6.0 beta 2 released

philwareham wrote #300517:

Board footer