English (United Kingdom)
Jms Multi Site, formerly joomla multisite.
Create, share multiple joomla sites in few clicks !
Message
  • EU e-Privacy Directive

    This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.

    View e-Privacy Directive Documents

Welcome, Guest
Please Login or Register.    Lost Password?
Go to bottomPage: 1
TOPIC: K2 image sharing bug
#4017
K2 image sharing bug 14 Years, 8 Months ago Karma: 0
Hi,

I don't know if this is a K2 or a JMS issue, but I stumbled upon the following:

When I add a K2 article to the master site and one to the slave site and it happens that they share the same K2 ID, the article content is different. This is what you should expect.
However, the image (uploaded via the K2 image tab) is shared. In fact, it will be shared between all articles in different sites that have the same ID.

I am not sure if this is a JMS issue and if you can do something on it.

Thanks,
Tom
ludder
Fresh Boarder
Posts: 18
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#4018
Re: K2 image sharing bug 14 Years, 8 Months ago Karma: 54
Tom alll depends how you have configured your slave site and if you have define a specific images directory for it or decided to share the images directory.

When you create a slave site, you can use a JMS template rule to have a specific images directory.
In this case, when you deploy the slave site into a specific directory, its images directory become specific. Otherwise, the images directory is shared wtih the master.

See tutorial video CP-05
edwin2win
Moderator
Posts: 5370
graph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#4030
Re: K2 image sharing bug 14 Years, 8 Months ago Karma: 0
My slave site has the following configuration:
- Path to image folder: {rel_site_dir}/images (so I thought it has it's own images directory now)
- The image folder of the slave is created with the option "Special copy". (I also tried this with the option "Copy".)

I did not however create a new deployment folder. Is that necessary to overcome this issue?
ludder
Fresh Boarder
Posts: 18
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#4031
Re: K2 image sharing bug 14 Years, 8 Months ago Karma: 54
JMS does NOT replace existing directory once it exists.
So if you have started to create a Symbolic Link on an images directory, it will remain a Symbolic link except if you delete it manually.

Some extension hardcode the "/images" directories and this is the reason why it is better to have a copy of the images folder in this case.
Very few extensions are reading the global configuration to get the image path.
So this may explain why you are still using the "images" folder as it seems that this is a link on your master.
edwin2win
Moderator
Posts: 5370
graph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#4034
Re: K2 image sharing bug 14 Years, 8 Months ago Karma: 0
I think you're right. K2 seems to use a predefined path to the media library...
ludder
Fresh Boarder
Posts: 18
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#5650
Re: K2 image sharing bug 14 Years, 1 Month ago Karma: 0
Hi,
I ran into the same problem. Did you manage to solve it by unsharing the media folder in the root and providing a special copy of it?
Or if you found another solution.. could you share it?
Thanks!
dustdog
Fresh Boarder
Posts: 6
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
Go to topPage: 1
get the latest posts directly to your desktop
2Win, Multisite(s) are trademarks of Edwin2Win.
Joomla