MultiSite Module Support Thread

[royaldave]

Is the module on github?
Then you could link to the commit.

I think it is on github, but I'm not - if that matters.

I need to my head around it one day.

[ideasgirl]

Hello, I've been using this module since version 1.0 and I'm doing an update from 1.5.5 to 2.1

The logs will show an error unless I change the line 29 of admin/multisite.php

from this:

while($multisite_cat_desc[0]=="\n") { 

to this:

while (!empty($multisite_cat_desc) && $multisite_cat_desc[0] == "\n") { 

Also, when assigning categories on the MultiSite Tool, I have a ">->-" before the name of the site assigned. In the previous version, those symbols didn't appear there. Is there a way to get rid of them?

[royaldave]

Hello, I've been using this module since version 1.0 and I'm doing an update from 1.5.5 to 2.1

The logs will show an error unless I change the line 29 of admin/multisite.php

from this:

while($multisite_cat_desc[0]=="\n") { 

to this:

while (!empty($multisite_cat_desc) && $multisite_cat_desc[0] == "\n") { 

Also, when assigning categories on the MultiSite Tool, I have a ">->-" before the name of the site assigned. In the previous version, those symbols didn't appear there. Is there a way to get rid of them?

Hi

I didn't write this plugin, although I have done the last couple of updates.

I'm very time poor of late and have not yet investigated how well this works under 2.1, that said I've acknowledged that the admin tool needs work in the documentation - it has been ignored for a very long time.

It is not essential to use this tool - you can manually update the category descriptions yourself and I'd recommend doing this until such time as myself (or somebody else) can fix it.

[royaldave]

I've discovered a bit of a loophole in multisite you might want to be aware of.

Background -

I might be imagining things, but I swear until recently if I pressed the back button on chrome it would reload the page it was going back to.

In recent times I've noticed it doesn't do this anymore, it goes back to a cached page. I've noted this in particular when switching off redundant products, ie I might do a search that will bring up that product, I go into that product to get that product id, and after switching it off in admin and pressing back, the removed product is still visible on the search page.

I think this may have changed in recent chrome updates.

Anyway why is this relevant you ask? Actually it might not be, but in the last week or so customers have been able to order products they should not have been able to - ie they've managed to checkout products that were in a different shop. (I'm using the distinct shopping cart option so this should not be possible)

After having a bit of a play I worked out that if for example your viewing a category, eg -

https://www.xxx.com/zencart/index.ph...index&cPath=26

and you change that cpath to a category that might be valid in one of your other shops then zencart will happily display it because this bypasses the cat_filter.

I'm guessing that recent browser updates might be allowing users to view a cached page that looks similar to one previously viewed. In any event I will look at how this can be tightened up.

And if you think i'm crazy please say so...

[pilou2]

And if you think i'm crazy please say so...

It might have started... Seeing you now are advertising ######## site in ZC forum... :)))

[royaldave]

It might have started... Seeing you now are advertising ######## site in ZC forum... :)))

oops. too late for me to edit too....

should've had my coffee first...

[royaldave]

Regrardless of my sanity, I have a solution to the little loophole I found - whether it solves the browser issues or not I don't know as I haven't been able to replicate it.

So in particular if you're using the distinct shopping cart option of multisite you might want to add this code to includes/modules/pages/index/header_php.php - this will prevent manipulation of the url giving the user access to a category that shouldn't be available in the shop they're browsing.

//bof multisite
//check that a cPath from another store is not attempting to be used.
    if ($cPath > 0) {
      $categories_query = "SELECT c.categories_id, cd.categories_name, c.categories_image, c.parent_id
                         FROM   " . TABLE_CATEGORIES . " c, " . TABLE_CATEGORIES_DESCRIPTION . " cd
                         WHERE      c.categories_id = :parentID
                         AND        c.categories_id = cd.categories_id
                         AND        cd.language_id = :languagesID
                         AND        c.categories_status= '1'
                         ORDER BY   sort_order, cd.categories_name";

      $categories_query = $db->bindVars($categories_query, ':parentID', $cPath, 'integer');
      $categories_query = $db->bindVars($categories_query, ':languagesID', $_SESSION['languages_id'], 'integer');
      $category_status = $db->Execute(cat_filter($categories_query));
      if ($category_status->RecordCount() == '0') {
        $current_category_not_found = true;
      }
    }
//eof multisite 

Put this in just above -

    // -----
    // Give an observer the chance to override the default handling for the category.
    // 

[royaldave]

I've discovered a bit of a loophole in multisite you might want to be aware of.



I'm guessing that recent browser updates might be allowing users to view a cached page that looks similar to one previously viewed. In any event I will look at how this can be tightened up.

And if you think i'm crazy please say so...

OK, i've discovered what the real problem is....

And it might depend on what your domain name is..

In my example I use multisite because I have geographic splits in my shop, so eg I've got perth.fb.com.au , adelaide.fb.com.au etc

If I google pokemon adelaide for example, and adelaide doesn't have it, but perth does, then google might yet give a result substituting the perth subdomain.

I think I'm affected by this because really I have one domain name and use subdomains for my shops - if you're using different domain names google might not do this.

Probably not many people affected by this, and if you're not using distinct shopping cart feature you probably don't care.

I'll have a think on the best way to approach solving this.