Marketplace update

blindmime
@blindmime
12 years ago
772 posts
Neither the Update All or the individual update buttons do anything for me. Tried in Firefox and Chrome. I have the id and email configured. Update went smoothly, no issues. I only FTP'd the core (not any modules from the super pack) and those are showing in the System Updates list as needing updates. I also applied the promo code and it discounts everything as it should it appears. I have Mac OS X 10.6.8. I'll try it on my Windows 7 laptop.
updated by @blindmime: 12/13/13 01:45:43PM
blindmime
@blindmime
12 years ago
772 posts
Not working there either.
michael
@michael
12 years ago
7,793 posts
no errors or issues in any of the logs? it just does nothing when you click on the buttons?
blindmime
@blindmime
12 years ago
772 posts
Nothing in the debug log or php error log. Clicking on an any of the Install buttons also doesn't work (the popups do work, but when I press OK they go away and nothing happens). The Purchase button work.
updated by @blindmime: 10/29/13 10:29:04PM
blindmime
@blindmime
12 years ago
772 posts
That's the Marketplace URL I have entered. I'm not getting any of the errors b is noting.
updated by @blindmime: 10/29/13 10:37:03PM
michael
@michael
12 years ago
7,793 posts
I'll do a fresh install now and see if i can match what your seeing.
blindmime
@blindmime
12 years ago
772 posts
I just purchased the Documentation module and it installed and took me to its module tab where I made it active.

Worked perfectly.
michael
@michael
12 years ago
7,793 posts
That's great to hear.

I'm still not setup with the fresh install yet, got sidetracked. Getting a move on now. :)
brian
@brian
12 years ago
10,149 posts
I've seen this once on an upgrade, and it appears to be a caching issue - the Marketplace javascript is not being pulled into the page until you do a cache reset.

I'm checking that out.

Thanks!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
brian
@brian
12 years ago
10,149 posts
This has been fixed in the latest jrCore 5.1.0 - root cause was that the javascript was not being rebuilt correctly after the module was enabled, so it took an integrity check again to get it working right. Should be good now though, so reload the Jamroom Core from the Marketplace -> Tools -> Reload modules and skins section and the fix will be applied.

I also fixed a small issue in the Marketplace browse template that will now correctly show "promo code applied" for items that have a promo code applied to them, so reload that module while you're in there too.

Let me know if you see any issues.

Thanks!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
blindmime
@blindmime
12 years ago
772 posts
Won't the Marketplace module be reloaded when you reload the core?

What's marketplace reloading/updating best practice when you've customized a skin? Also, if you've customized module templates will they be safe? If I do Update All, is it going to update the skins as well?

Just sort of wondering how all these things play together, I guess.
updated by @blindmime: 10/30/13 07:53:05AM
brian
@brian
12 years ago
10,149 posts
If you've made your skin changes using the online template editor, all those changes are stored in the DB, so are never overwritten.

If you've modified one of the skins (say jrNova) and do NOT clone it first, but instead just modified the templates directly, your templates will not be overwritten UNLESS you do a "reload". If there is a version upgrade (say going from 1.0.1 to 1.0.2), then the old version (1.0.1) is placed into a backup "release" directory, and the new version is downloaded and activated. This let's you "rollback" if needed.

But if you just go into Tools -> Reload modules and skins and do a reload on the SAME version, then your changes would be overwritten by the update.

So best practice would be to first CLONE the skin you want to modify, and make your changes in that skin - that way it can never be overwritten. Then, when new releases come out for the skin you based yours on, you can just do a compare to see what has changed and update if needed.

Let me know if that helps.

Thanks!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
blindmime
@blindmime
12 years ago
772 posts
What about module templates you've altered?
brian
@brian
12 years ago
10,149 posts
Same thing - module and skin updates work the same way. If you made those changes in the online template editor, you have nothing to worry about. If you've modified the .tpl files directly, they will get overwritten if you do a RELOAD. If it is an upgrade (i.e. going from one version to the next) they are not overwritten, but instead the entire module directory is renamed and saved - i.e. if you updated the "profile forum" module for example, after the update you would see something like this in your modules directory:

jrForum -> jrForum-release-1.0.2
jrForum-release-1.0.2
jrForum-release-1.0.1

So the "active" jrForum module is a symlink that points to the 1.0.2 release, wile the previous 1.0.1 release is saved in the jrForum-release-1.0.1 directory, so you could copy any of your changes from that directory into the active one.

Let me know if that helps.

Thanks!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
blindmime
@blindmime
12 years ago
772 posts
I'm having trouble updating these:

Email Newsletters 1.0.1 1.0.3 changes stable fail
jrFoxyCart FoxyCart eCommerce 1.0.1 1.1.0 changes stable fail
jrCharts Advanced Charts 1.0.1 1.0.2 changes stable fail
jrForum Profile Forum 1.0.0 1.1.0 changes stable fail
jrOneAll OneAll Social Link 1.0.1 1.1.0 changes stable fail
jrSoundCloud SoundCloud Support 1.0.1 1.0.3 changes stable fail
jrComment User Comments 1.0.0 1.1.0 changes stable fail
jrPrivateNote Private Notes 1.0.1 1.0.2 changes stable fail

I get the progress spinner, then it goes to the Page Not Found page. When I return I have a warning message: "Invalid Module License - please refresh the System Updates tab and try again"
brian
@brian
12 years ago
10,149 posts
Yeah right now the "update all" isn't handling errors in the underlying update properly - I'm working on that, so for now I'd just do them one at a time until I get those fixed.

Did you purchase those modules as part of the Super Pack? The license should have automatically been setup for you on the backend, but I can check that out.

Thanks!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
brian
@brian
12 years ago
10,149 posts
Okay just checked out your licenses, and you do have good licenses for all of these, so it's an error on the backend - let me figure out what is causing this and I will get it fixed.

Thanks!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
blindmime
@blindmime
12 years ago
772 posts
No problem, Brian. jr5 is awesome. That word is overused, but it applies in this case. I am in awe of what the Team has done and is doing. Brilliant work, exciting possibilities.
brian
@brian
12 years ago
10,149 posts
Right on - that means a lot and is really appreciated!

I've got the backend fixed now - go into your System Updates tab and refresh your browser - this will re-request the info from the backend, and the licenses should be linked properly - this should let the update complete.

Let me know if that works.

Thanks!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
blindmime
@blindmime
12 years ago
772 posts
Perfect -- thanks, Brian.
michael
@michael
12 years ago
7,793 posts
blindmime:What about module templates you've altered?
Just a quick word on this, in case you weren't aware; If you don't want to use the online template editor and want to alter a modules template, the way to do it is to over-ride it at the skin level.

So if you wanted to change:
/modules/jrAudio/item_details.tpl

You could create:
/skins/xxYourSkin/jrAudio_item_details.tpl

and it would over-ride the jrAudio modules version.

Tags