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
Please verify that the file system location given in the “File directory path” advanced preference is definitely the one where these files are stored.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
Yes false alarm. Updated the site earlier today and thought I had entered the correct path to /files….oops! Thanks wet.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
Set a file in the Files tab to “hidden” or “pending” then use the Download link on the left of the File List screen (or click its hyperlinked name on the File Edit screen). On my site it triggers a public-side 404 message and I get a tonne of TXP errors on screen (“Article tags cannot be used outside an article context”) because it failed to process the file_download.
EDIT: This may actually be related to the behaviour Mary fixed (at my behest, gulp) a looooong time ago, I’m not sure.
Last edited by Bloke (2008-11-22 16:21:38)
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
Bloke wrote:
Set a file in the Files tab to “hidden” or “pending” then use the Download link on the left of the File List screen (or click its hyperlinked name on the File Edit screen). On my site it triggers a public-side 404 message
Good. This is the expected behaviour.
and I get a tonne of TXP errors on screen (“Article tags cannot be used outside an article context”) because it failed to process the file_download.
Ugly, but I cannot see this happen with the default page templates. All I see is just the familiar error_default page.
EDIT: This may actually be related to the behaviour Mary fixed (at my behest, gulp) a looooong time ago, I’m not sure.
I guess you’re right.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
A minor point. On the “Write” tab, under “Advanced Options” all the “help” links are alongside the titles except for “Override form” which for some reason is placed after the “select”. Looks a little untidy methinks but it is even more of a pain in the arse if you are trying to do a re-style. ;)
Stuart
In a Time of Universal Deceit
Telling the Truth is Revolutionary.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
Also, whilst you are there, and this is more a request than anything wrong, any chance of giving the “More” link paragraph (under “Textile Help”) a class of it’s own please?
Stuart
In a Time of Universal Deceit
Telling the Truth is Revolutionary.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
About glz_custom_fields, is there now a non- hack work-around to get more than ten custom fields? In 4.0.6, it was necessary to modify the publish.php file:
<?
function getCustomFields()
{
global $prefs;
$out = array();
$i = 0;
$custom_fields_num = count(preg_grep("(^custom_\d+_set$)", array_keys($prefs)));
while ($i < $custom_fields_num) {
$i++;
if (!empty($prefs['custom_'.$i.'_set'])) {
$out[$i] = strtolower($prefs['custom_'.$i.'_set']);
}
}
return $out;
}
?>Is this still the preferred method? Would something like this ever make it into core?
Thanks!
Last edited by johnstephens (2008-11-22 17:39:52)
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
johnstephens wrote:
About
glz_custom_fields, is there now a non- hack work-around to get more than ten custom fields? In 4.0.6, it was necessary to modify the publish.php file:Is this still the preferred method? Would something like this ever make it into core?
Yeah, I second that. Not that I don’t like hacking and all…
Last edited by mrdale (2008-11-22 18:14:32)
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
Wrong place to mention this, but isn’t it about time we got a “save new” button on the default install.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
thebombsite wrote:
A minor point. On the “Write” tab, under “Advanced Options” all the “help” links are alongside the titles except for “Override form” which for some reason is placed after the “select”.
I’ve changed this but I would need a few cross browser tests for any jumping form elements upon toggling “Advanced” options and such, especially with edge cases, i.e. cases where the contents of select options or input boxes exceeds the element’s width.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
johnstephens wrote:
Is this still the preferred method? Would something like this ever make it into core?
mrdale wrote:
Yeah, I second that. Not that I don’t like hacking and all…
Thanks!
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
Please refrain from off-topic postings. We are trying to build a final release here, and adding noise to the signal does not help.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
Thanks Robert. I’ll give it a few tests with different browsers when I’ve uploaded iit. I’ll post back.
Last edited by thebombsite (2008-11-22 19:05:40)
Stuart
In a Time of Universal Deceit
Telling the Truth is Revolutionary.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
wet wrote:
Please refrain from off-topic postings. We are trying to build a final release here, and adding noise to the signal does not help.
OK Dad.
Offline
#45 2008-11-22 21:44:55
- Logoleptic
- Plugin Author
- From: Kansas, USA
- Registered: 2004-02-29
- Posts: 482
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
I have a question about the new template parser. I’ve built a handful of sites that rely, sometimes heavily, upon asy_wondertag’s tags-as-attributes feature. Since the new parser has this feature built in, will the wondertag plugin stop working? It’s great to have the feature by default now, but I’m wondering how much template rewriting I should plan for as sites get upgraded.
I’d test this myself, but I’m wrapped up in a high-priority project all weekend. I can’t be the only one facing this situation, though. If anyone can find an answer you’d be helping out a lot of wondertag users. Thanks!
Offline