-
☆ A M B ☆
- 24,524 Posts
On a side note, looking at your site a while ago, I read your "foolproof bread" recipe. You recommend a cylindrical bowl, so I immediately ran and checked to make sure that I hadn't thrown out my old crock-pot. The liner makes an excellent bread-making and proofing container. And I have a nice cast-iron dutch oven for the baking. Cast iron does give everything such a nice flavor!
I use hand-ground whole-wheat flour, though.
-
☆ A M B ☆
- 24,524 Posts
Ok. It won't install at all on Revo 212, too many deprecated functions used in Revo 212, and there doesn't appear to be customizable Dashboards anyway.
So far tried up to 2.2.10
Attempting to install package with signature: upgrademodx-1.0.1-beta1
Package found...now preparing to install.
Grabbing package workspace...
Workspace environment initiated, now installing package...
PHP warning: preg_match(): Compilation failed: invalid range in character class at offset 38
PHP notice: Array to string conversion
chunk_err_createArray
Error saving vehicle object of class modChunk; criteria: Array ( [name] => UpgradeMODXTpl )
PHP warning: preg_match(): Compilation failed: invalid range in character class at offset 38
PHP notice: Array to string conversion
chunk_err_createArray
Error saving vehicle object of class modChunk; criteria: Array ( [name] => UpgradeMODXSnippetScriptSource )
PHP warning: preg_match(): Compilation failed: invalid range in character class at offset 38
PHP notice: Array to string conversion
snippet_err_createArray
Error saving vehicle object of class modSnippet; criteria: Array ( [name] => UpgradeMODXWidget )
Could not install related objects with locally owned keys for vehicle object of class modCategory; criteria: Array ( [category] => UpgradeMODX )
Successfully installed package upgrademodx-1.0.1-beta1
[ed. note: sottwell last edited this post 11 years, 1 month ago.]
-
☆ A M B ☆
- 24,524 Posts
Installs fine in 2.2.16, but download and/or extraction fails. No "setup" folder. And now the Manager white-pages.
-
☆ A M B ☆
- 24,524 Posts
Tried it on a 2.3.6 installation. All is well until extraction. Getting this Apache error:
[Tue Aug 25 08:34:20 2015] [error] [client ::1] client denied by server configuration: /Applications/MAMP/htdocs/.DS_Store
Original install.php script works fine.
-
☆ A M B ☆
- 24,524 Posts
Tried it on a 2.3.5 installation on SkyToaster (the previous .DS_Store issue is a Mac thing). Installed fine, but attempting the Dashboard gets this results:
Fatal error: Can't use method return value in write context in /home/babyrooc/public_html/core/cache/includes/elements/modsnippet/66.include.cache.php on line 168
Seems a bit odd, that line is just
if (empty($this->getErrors())) {
[ed. note: sottwell last edited this post 11 years, 1 month ago.]
@Sottwell. It depends on your version of PHP. Here's the fix:
$e = $this->getErrors();
if (empty($e)) {
I've released 1.0.2-beta1 with the fix.
@Jako, my widget does tell you about available upgrades to MODX, but it doesn't deal with package updates. If you want to know about available package updates in the dashboard, I think you'd have to use both widgets.
I just realized that I've hijacked Inreti's thread. My apologies. I've started a new topic for UpgradeMODX.
https://forums.modx.com/thread/98111/support-comments-for-upgrademodx-1-0-2-beta1#dis-post-530520
[ed. note: BobRay last edited this post 11 years, 1 month ago.]
-
☆ A M B ☆
- 1,031 Posts
@BobRay: Does your widget create a link to a CMP or to another page that starts the updating process? If yes, could another package create that link with a $modx->getService + a class method? Then Updater could use that link if UpgradeMODX is installed.
My widget creates a file based on PHP code in a chunk, then launches it. This makes things more secure because the file isn't there until it's needed and it's deleted after the install.
Any extra could use that code to write its own file, but it would have to replace the single placeholder for the array of versions to be shown. I create that array in the widget so the upgrade script doesn't have to spend time on it. It's more efficient because the widget already has the data from it's check for upgrades.