0962 is up next

7,075 Posts

davidm Reply #31, 18 years, 8 months ago

Good point... could they be displayed according to the user role ?
That would solve it...

.: COO - Commerce Guys - Community Driven Innovation :.

MODx est l'outil id

☆ A M B ☆
24,524 Posts

sottwell Reply #32, 18 years, 8 months ago

Or it might even be simpler to only have it show for Administrator users (role 1)

Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org

☆ A M B ☆
1,056 Posts

pixelchutes Reply #33, 18 years, 8 months ago

I think Ryan was going to see if ScottyD had some availability for developing a "config module" for this implementation. Possibly he could use some/all of the recommendations here??

Mike Reid - www.pixelchutes.com
MODx Ambassador / Contributor
[Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
________________________________
Where every pixel matters.

MODX Staff
12,272 Posts

Ryan Thrash Reply #34, 18 years, 8 months ago

Where is that darned Pirate when you need him?

Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me

☆ A M B ☆
24,524 Posts

sottwell Reply #35, 18 years, 8 months ago

Pirates generally show up when you least expect them grin

Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org

MODX Staff
12,272 Posts

Ryan Thrash Reply #36, 18 years, 8 months ago

Please take a quick peek at the bugtracker. I’m inclined to have bugs that are marked 100% as closed out. I’ve typically found that most folks don’t respond once they make a bug report and tickets sit open for a long time waiting for feedback that never comes. If there’s a reason to keep it open, ratchet them back to 90%, but let’s close some of these things out and start attacking the critical/major/high reports and get 0962 into a test release ASAP.

Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me

7,075 Posts

davidm Reply #37, 18 years, 8 months ago

I seem to remember we do get notification when a comment is published with FlySpray though... funny people don’t respond huh

Though I confess, I have not been as active as I have been in the past in that department tongue

Edit : Did the "Bugs" buttom on top right of the forums disappear ?

.: COO - Commerce Guys - Community Driven Innovation :.

MODx est l'outil id

MODX Staff
12,272 Posts

Ryan Thrash Reply #38, 18 years, 8 months ago

"Bugs & Support" link?

Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me

MODX Staff
12,272 Posts

Ryan Thrash Reply #39, 18 years, 7 months ago

Can someone take on the task of restoring proper functionality to the installer to allow for selective installation/updating of resources? Now it is all or nothing.

Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me

4,205 Posts

dev_cw Reply #40, 18 years, 7 months ago

The problem is in the action.summary.php file. The block begining at line 228 is not setting the array for the options correctly. I changed it as follows (changing the value="{$i}" to value="$snippet"). All seems to be working on my test environment, please confirm.

<?php
$templates = isset ($_POST['template']) ? $_POST['template'] : array ();
foreach ($templates as $i => $template) echo "<input type=\"hidden\" name=\"template[]\" value=\"$template\" />\n";
$chunks = isset ($_POST['chunk']) ? $_POST['chunk'] : array ();
foreach ($chunks as $i => $chunk) echo "<input type=\"hidden\" name=\"chunk[]\" value=\"$chunk\" />\n";
$snippets = isset ($_POST['snippet']) ? $_POST['snippet'] : array ();
foreach ($snippets as $i => $snippet) echo "<input type=\"hidden\" name=\"snippet[]\" value=\"$snippet\" />\n";
$plugins = isset ($_POST['plugin']) ? $_POST['plugin'] : array ();
foreach ($plugins as $i => $plugin) echo "<input type=\"hidden\" name=\"plugin[]\" value=\"$plugin\" />\n";
$modules = isset ($_POST['module']) ? $_POST['module'] : array ();
foreach ($modules as $i => $module) echo "<input type=\"hidden\" name=\"module[]\" value=\"$module\" />\n";
?>

However, I noticed another bug. When using the back button from the install summary page it will not select the actual selected options, instead it will select the first number of options acording the the number selected originally. For example is you select 4 snippets, on clicking the back button it will select the first 4 rather the the actual 4 you selected previously.

[font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

Something is happening here, but you don't know what it is.
Do you, Mr. Jones? - [bob dylan]