Hi Abolabo,

My apology for not being clear.

When trying to use as single interface I was only login by default store domain.
It is only this login that shows store selector and store selector does show default store and second store is shown in drop down.
Single interface could not be used from login to second store domain as there is no store selector available when logged in by second store domain.

When store selector is used to select second store then settings for second store are shown.
If store selector is used again to try and select default store then the "stuck" problem occurs as second store settings are still shown.
Now if I log out and then log back in second store settings will still be shown - store selector will be showing second store, on drop down default store.
If I select default store in drop down again second store settings will show.

I can repeat this with with system cache clear and browser cache clear, but login to default store domain will still show second store settings and using store selector to attempt change back to default store will result in still second store settings.

If I leave the system alone for a few hours and home back, login to default store domain then the system has reverted itself and default store settings are shown, store selector shows default store with second store in drop down.

I hope this explanation clarifies.

Regards,
Tastiger.

Hi Basra,

Yes, I have witnessed admin working from the one interface but found that when I change from default to the second store the admin becomes stuck in the second store even between logins meaning I can no longer administer default store :-( This is where it is stuck now after trying in single interface.
 
So my work around last few months has been to log into admin of each store under its respective domain. Under one admin is fine if I can get it to go back and forth.

Regards,
Mark

Hi Abollabo,

Thanks for assisting.

The config.php has been replace in /core/lib/

The result is when using the url for second store admin it no longer gives error but it enters default store admin instead of second store admin even though the url stays on the second store domain.

Thanks,
Tastiger

Hi Soup,
I couldn't find a way either, but I did find that I could achieve content in the main menus. Simply build your content menu structure as categories and use category descriptions for your content. See the Advocacy menu on my website.
Cheers,
Tastiger

Hi Soup,
I found quit a lot can be done with AbanteCart. I built my basic website with using content pages and categories as pages. Have a look at how AbanteCart works with layouts and blocks and I am sure something will come to mind for how to form a video gallery and design document pages. I did end up using Wordpress for the blog though in hindsight I think my blog could have also been achieved within Abantecart. In time I learn more and maybe achieve holding everything in AbanteCart.

Hi Dante,

Could you use developer tools to duplicate default fixed rate extension to make the other fixed rate choices you need?

I have set up a multistore and modified it for use as POS with receipt printing.
The main website also makes use of the basic pick-up and pay-instore extensions made.

It is proving quite effective for our needs as a small volume home shop and a lot cheaper than running Vend like we used to!

Maybe somebody talented could extend multi store to provide a more fully featured pos or an integration to Vend or Kounta be developed.

- Mark

Hi Zer07even,

My cache permissions problem now seems resolved by approaching it as actually being a delete issue. I have not had a permissions error for for some time now and there has been increasing activity on the site.

Folder permissions are 777 ,cache files are created with permission 644 - these should not be changed, only folders.
After setting your folder permissions to 755 clear your cache.
I think the trick may be to then check your cache folders straight away for any stray 644 files and manually delete them via FTP or Cpanel.
Then any new cache files the system create it should also be able to delete correctly now under the folders with 777 permission. It is when the delete does not happen correctly (or in a timely manner) that the replacement, updated cache file cannot be written generating the error even with folders set 777

- Mark