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
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
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
The wondertag plugin still works. I’ve been testing some of my old sites with the 4.0 dev version, and they work side by side. Using smd_where_used you can easily go through and nip out each instance in your own.
I also relied heavily on chh_if_data, which is no longer needed if you use txp:if_variable. That plugin works too.
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
Has anyone tested 4.07 with glz_custom_fields and any other advanced plugins?
Offline
Re: Feedback to: Help us test the release candidate for the upcoming 4.0.7
The default first article points to the “Textbook Wiki” – a page which doesn’t exist yet.
Offline