How to solve the problem with bulk password requests in members area

Attention:
this instruction is only for the cases when:
a) is used centralised content for several member zones at once;
b) the content is located in SUBDOMAINS, not in SUBFOLDERS.


Attention:
if you use:
a) Lite edition, or
b) separated content for each site, or
c) centralised content for several member zones, BUT content is located in SUBFOLDERS and simlinks are adjusted
YOU HAVE TO MAKE NO ACTIONS!


The problem explanation:

Latest browsers version defines the content subdomain as separate domain name and asks for extra password for each page element taken from there. In order to solve it your page should take the content from the same domain where the loaded page is. For example, now you have:
members area at:
http://paysitedomain1.com/members/
content at:
http://content.paysitedomain1.com
- you have bulk password requests. However, if members area and content will be at:
http://paysitedomain1.com/members/
http://paysitedomain1.com/content/
- even if each folder will has separated .htaccess - the password will be asked only once in members area. And the content items will be still protected from direct unauthorised access.



What to do:

1) You have request your sysadmin or hoster tech-support to adjust simlink from:
http://paysitedomain1.com/content/
to
http://content.paysitedomain1.com/

Thus the picture physically located at:
http://content.paysitedomain1.com/picture.jpg
can be loaded in browser as:
http://paysitedomain1.com/content/picture.jpg
That's how you can check that simlink has been adjusted correctly.

If you have several paysites, you have to have simlinked folder /content/ at each paysite domain. i.e.:
http://paysitedomain1.com/content/
http://paysitedomain2.com/content/
http://paysitedomain3.com/content/
and all of em should be adjusted as simlinks to the REAL content location:
http://content.paysitedomain1.com/

2) Make global modification in MySQL database which is used by aWIZ script:
a) make backup of existing MySQL database and keep it reserved!
b) make a dump of the following tables in sql format: sets, favorite, favorite_vote, vote.
c) open the dumped files in text or HTML editor and make global change by adding the /content/ subfolder between domain name and further part of url, and remove subdomains from the urls. F.ex. you have records:
http://content.paysitedomain1.com/sets/pictures/alice/
it should be changed to:
http://paysitedomain1.com/content/sets/pictures/alice/ (* - read below)


NOTE : only URLs should be edited! The paths should stay with no changes.

3) Open the admin-panel section "Domain-specific setup for ..." all your domains, and make sure that the field "visible Domain" is filled with the current domain name (without "http", "www" or slashes!).
* - particular case:
If your members areas also are located at subdomains (like http://members.paysitedomain1.com) - you haven't to remove subdomain name (in current example the word "content") from the content URLs database records.
Comments:
1) We strongly recommend to make a test change in several sets details and test it in members areas before to rework all database.
2) If you have no experience in database works, you can order us this modification and members areas reorganisation on the custom base.