Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Parts of backend not functioning after update
Guys, the site seems to function somehow. This error will appear but it’s not critical and they have no budget for more. It’s enough of a pain that I have to deal with the ugliest TXP state of a site I have seen till now. How could people make such a mess!?
Anyway. Thank you a ton for the help! It feels like home here, always.
Offline
Re: Parts of backend not functioning after update
We should probably ditch it wholesale in core. Options:
- GlobIterator (though it’s unclear if it can iterate over files with multiple patterns).
- Loop by hand with a DirectoryIterator or FilesystemIterator.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: Parts of backend not functioning after update
datorhaexa wrote #308354:
This error will appear but it’s not critical
It’s only a warning. Will disappear when you put the site in Live mode.
We’ll find a way to work around it… maybe even sneak a fix it into 4.7.0 since we’re doing all manner of Language things there anyway.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: Parts of backend not functioning after update
Offline
Offline
Re: Parts of backend not functioning after update
etc wrote #308357:
+1
Let’s do that then. If you have ten mins today, please feel free to replace any glob() calls with that. If not, I’ll tackle it (probably tonight if I can).
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Offline
Re: Parts of backend not functioning after update
datorhaexa wrote #308360:
I seem to be the unsuspecting tester.
We have a lot of those ;-) That’s what makes Txp so rock solid.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: Parts of backend not functioning after update
Bloke wrote #308359:
Let’s do that then. If you have ten mins today, please feel free to replace any
glob()calls with that. If not, I’ll tackle it (probably tonight if I can).
It does not seem to filter by a mask, so we can also just do two or three glob() calls, or even glob everything and filter manually for lang directory.
datorhaexa wrote #308360:
I seem to be the unsuspecting tester.
You’ll be if you install 4.7. And welcome home btw :-)
Offline
Re: Parts of backend not functioning after update
etc wrote #308362:
It does not seem to filter by a mask
Nope. So either mechanism you mentioned works for me, whichever is most efficient/neatest.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: Parts of backend not functioning after update
Done it in Lang.php (4.7), but not (yet) in setup, since we have spoken of removing themes directory from there anyway? If so, only one directory has to be scanned, hence no need fo GLOB_BRACE.
Offline
Re: Parts of backend not functioning after update
etc wrote #308364:
Done it in
Lang.php(4.7)
Awesome! Great solution to fall back on an iterator if GLOB_BRACE isn’t available.
but not (yet) in
setup, since we have spoken of removingthemesdirectory from there anyway?
I can’t remember actually, but I think we decided to only ship public themes in the setup directory and not with the main 4.7 themes directory. This is so that we don’t potentially overwrite anyone’s sites, as there’d be no simple way to ‘sync’ the file system with the DB on upgrade (short of forcing an export, which seems a bit risky for anyone who’s running 4.7.0-dev and has started playing with themes already).
Can’t recall for sure, but I think that was the outcome. So we should be able to do the same trick in setup.
EDIT: Might even be some code reduction to be had here, when Themes is merged, as we could possibly use the Theme API to handle content loading. Probably should check the Themes does this glob fallback too.
Last edited by Bloke (2017-12-19 14:08:42)
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline