Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
jstubbs wrote:
Robert, not meaning to be pushy, but have you seen my earlier post?
Sure. Are you able to add an additional new image?
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
Yes, I am. It took the #id of 696, which is the next in line from what is displayed in the Images tab. However, I think #696 already existed in the folder :-(
In the images folder, I can see images up to #id 773 using Coda. The images open in preview too.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
Precondition: The content of the /images folder is not the source for the image tab’s list. The image tab’s list is built by reading all entries in the txp_image database table.
So it looks like at one point in time the amount of “recorded” images (kept in the database) and the amount of image files in the folder started to diverge. Are you able to skim over the txp_image table with phpMySQL or a similar tool and verify the content and amount of rows there?
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
Yes Robert, I figured out the same thing. I imported the DB over, but not quite sure what happened with the txp_image table. I will work on it tonight when back from work, and report back. Thanks for your help.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
wet wrote:
No, but it could be a timing issue.
Thanks for clarifying, Robert. Missed your post. Downloaded and installed 4.0.6 on Nov., 18. (AFAIR)
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
sthmtc wrote:
Downloaded and installed 4.0.6 on Nov., 18. (AFAIR)
This explains the symptom: We update development versions’ database structures by comparing some file modification dates to a date which is recorded when the site’s latest installation took place. By installing the older 4.0.6 “too late” the update procedure didn’t run. This would not happen in real life, neither with the final 4.0.7 release nor with an aged “real” 4.0.6 site from earlier this year.
Nothing to worry about.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
changeset 3016
Filenames should be preserved as much as possible now. It strips potentially harmful or illegal characters, but no longer attempts to create filenames that are free of url-encoded characters (the user can still do this himself by supplying an URL-friendly filename).
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
ruud wrote:
Filenames should be preserved as much as possible now.
Good move, thanks… except I used that handy sanitizeForFile() function a few times in one of my upcoming plugins, and now the function’s been dropped… dammit!
No bother, I’ll just have to duplicate the regexes you’ve used inline in r3016 instead.
EDIT: unless you fancy putting those two lines inside a new sanitizeForFile() function so we have an official mechanism for dumbing down filenames… :-)
Last edited by Bloke (2008-11-25 16:53:05)
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
… just a little typo in textpattern.css:
fieldset { …
border: 1px solid #ddd;;
}
;~)
Offline
#100 2008-11-25 17:21:57
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
Danke, Welt gerettet.
Offline
#101 2008-11-25 17:27:00
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
mit den kleinen dingen muss man anfangen.
it’s all about the little things.
Offline
#102 2008-11-25 19:58:48
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
Robert, confirmed that I overwrote the txp_images table by mistake, which resulted in many images not showing in the Images tab. ;-)
Offline
#103 2008-11-25 21:53:08
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
Not sure if this qualifies as 4.0.7 feedback per se…
I have a fix for the asy_jpcache plugin that allows it to respect 404 status returned by Textpattern. However, the plugin needs a way to learn that Textpattern has returned a 404 status code. The simplest and cleanest method I have devised involves a one-line addition to function txp_status_header in file txplib_misc.php to send a custom header that can be read by the plugin as follows. Would it be possible to add this in to the 4.0.7 release?
function txp_status_header($status='200 OK')
{
header("Txp-Status: $status");
if (IS_FASTCGI)
header("Status: $status");
elseif ($_SERVER['SERVER_PROTOCOL'] == 'HTTP/1.0')
header("HTTP/1.0 $status");
else
header("HTTP/1.1 $status");
}Offline
#104 2008-11-25 23:05:46
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
^^ It’s far too late to change something like that now.
Offline
#105 2008-11-25 23:29:54
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
ruud wrote:
^^ It’s far too late to change something like that now.
I suspected so. Will submit a patch to the dev list.
Offline