Im trying out a bunch of components for a new site im about to build, before chosing which components to use.

On the domain i have 2 almost identical sites for testing, same Joomla version and same template. On one of the sites Discogs and Scan a folder works perfect and on the other site nothing happends when i click these buttons.

The difference between the sites is that the one where it doesnt work have a few more components installed for testing. The 3 components that differ are: JoomSocial, Zoo and JCEditor.

My guess is that one of these components (or any plugin) isn't compatible with Music Collection. Testing still to be done though

sorry,
can you send me your Music Collection order ID? you don't appear on our system as a customer...

Germi

Hey Germi,

Im building a site for a client of mine.
im not sure of their client id but i know their user name that they would have signed up with would be

comikudos does that help?

We're experiencing the same problem with discogs, could u pls advise?
site is www.musicbailout.net, mootools upgrade is disabled in the plugins.
thanks in advance.

@thinkcloud yes, this username is indeed a verified user. please try to login with that account for now on (we can only give support to verified accounts...)

1) can you verify that mod_gzip is enable on your Apache server?
2) what happens when you try to search for something? does something shows up? or it just doesnt happen anything?

besides of that, we have a beta solution based on CURL that seems to work good so far. if you want to try it let me know and I'll send the file.

Just F.Y.I
Disabling the Plugin 'System - Mootools Upgrade' immediately solved all problems with MC on my testing site Discogs + Scanning works again..

Heya Germi.

Thanks for all you help with this.
It has been an uphill battle with the client. At the end of it all, the hosting provider he has signed up with wont turn on Gzip on shared hosting.

ANYWAY i told the client it was their hosting providers fault and not the components.



However i do have one outstanding issue.

My only question is why when uploading songs why do Disc Num and Song Num default to a max of 127 if you put a larger value in say like 999?

Can you please tell me how to make this bigger or remove it.

ive had a look and im no noob when it comes to php but maybe im looking in the wrong area because i cant find it.

See attached screen grab to see what i mean


Thanks for your speedy help in advanced

Also discovered a problem with DISCOGS search. Once introduced the album name and clicked search, the Nigo at first glance did not happen. But it turns out discogs plugin to create an XML data file to search far beyond the domain folder. For example I'm using virtual hosting. There's the root folder, this folder is a folder "domains", and in it are already in the folder-type "site.com". I understand that the plugin should save the file to "site.com", but it saves a file at all in the root directory. This could be the problem?

@hypo999 mmm.. I don't know.. it could be.. I'll take a look.
the results do not load at all?

@thinkcloud are you a Music Collection customer? you don't appear on our system as a customer.. (look at the notice under your profile on the left of the forum topics)

Germi

Hey Germi,

Im representing one of my clients.
i can PM you the clients details if you dont believe me.

the name the client signed up with is comikudos

of course I believe you and I checked this username and its OK.
it's just that I have to check it first you know! nothing personal!

the thing is that now I know your a verified user... but maybe in a couple of weeks or a month I'll forget that (we have soo many users... I can't remember all of them!) so I may ask you that question again...

to avoid it, my suggestion is, please, if you can, log in with your client's account...!! that will save both you and me a lot of time!!

about your question:

it is a limitation on the DATABASE field.
if you go to your MySQL manager (phpMyAdmin for instance) and open the table jos_muscol_songs, teh fields NUM and DISC_NUM are of type TINYINT
whic allows a max of 127

so you need to change these fields to INT

for instance INT(11)

you'll have no limits then!

best,
Germi

Wow what a stupid small over sight on my behalf.
i even looked at the DB before i asked you the question :/

sorry haha but i cause i just assumed it would be a bigger issue than that.
haha thanks heaps