Hm. Same problem.
Very odd; the same queries (with the {PREFIX} changed to modx_) seem to work just fine individually in phpMyAdmin.
Even odder... I removed the set of queries for the site_plugin_events, and it installed just fine.
-
- 22 Posts
Just uploaded a new file, the problem was that in the install file each command should be followed by a blank line...thats why it works in phpMyAdmin and not on the install file.
The new sql also includes a fixed mm_demo_rules query and those 2 tpls with direct links spotted by iusemodx.
Many thanks,
Let us know if ok...
Regards,
Jo.
Mojopea Team.
Ah. I knew it had to be something simple/silly like that. I just didn't see it; hadn't quite gotten to the point of asking myself "why is this knight not like every other knight..."
manager/actions/resources.static.php doesn't need to be modified to add the custom css and javascript. The mm_rules chunk can take PHP code, so you can use the appropriate $mdox->regClientScript() API function there to insert your custom css and js files. Or use them in a plugin, whichever seems best.
Instead of adding the custom css file to the default MODxCarbon style, it would be better to duplicate the MODxCarbon style with your own name, and modify the style.css as necessary. Set the Manager to use your style. Then you wouldn't need to add the link to the custom css file at all. Plus no worries about site upgrades messing with your custom styling.
By the way, ManagerManager installs its own jquery library; you can modify the jquery source in its plugin configuration.
Still getting the fatal PHP error from this line
public function get_payment_params($call_function, $_GET){
The error is
[22-Jun-2013 17:25:39 Europe/Berlin] PHP Fatal error: Cannot re-assign auto-global variable _GET in /Applications/MAMP/htdocs/mojopea/assets/snippets/cartsnippets/MojopeaActions/snippetsClass.php on line 1232
That is called "shadowing" a superglobal, and since PHP 5.4 you can't do it.
Um... since it's a superglobal, it's always available. Why do you need to pass it as a parameter to a function?
[ed. note: sottwell last edited this post 10 years, 10 months ago.]
-
- 953 Posts
Some thoughts:
1)
For the store settings (ID 1006) "Store Page Numbers" tab I would suggest using exactly the same names as used in the pages themselves e.g
PRODUCTS MASTER PAGE => PRODUCTS
COUNTRIES PAGE => COUNTRIES EDITOR
OPTIONS PAGE => OPTIONS EDITOR
I found when looking for the ID I looked at the name in the tree and then looked for the ID if I couldn't see the name first.
2)
I initially forgot to upload the files for the manager, and realised it all still worked in the back-end without the fancy menu look
Would it not be better to give the user the option to use or not use the fancy menu when installing the system ?
Also, if the manager files are overwritten, updates will cause problems as the files will be overwritten again.
More to come - possibly
Cheers
[ed. note: iusemodx last edited this post 10 years, 10 months ago.]
Indeed. One should never hack core code. If something as major as a good e-commerce solution really does require a core code hack, the best way to handle that is to make is as generic as possible, then offer it as a pull request to github and get it into the core.
But considering how well ManagerManager works, I think some creative Javascript could be used to modify the Tree in the browser via the DOM in the same way that ManagerManager works for resource editing. After all, the ID of the resources in question are known from the installation.