1
chefry
Updating Cloned Publisher
  • 2013/5/27 11:32

  • chefry

  • Home away from home

  • Posts: 1005

  • Since: 2006/10/14


How do I run an update for a cloned publisher module?

I installed the original publisher, then cloned it with different names

How can I update these?

2
Mamba
Re: Updating Cloned Publisher
  • 2013/5/27 11:56

  • Mamba

  • Moderator

  • Posts: 11366

  • Since: 2004/4/23


Just update your Publisher, and then clone it again.
Support XOOPS => DONATE
Use 2.5.10 | Docs | Modules | Bugs

3
chefry
Re: Updating Cloned Publisher
  • 2013/5/27 12:45

  • chefry

  • Home away from home

  • Posts: 1005

  • Since: 2006/10/14


that won't wipe out the existing databases for the cloned modules?

4
Mamba
Re: Updating Cloned Publisher
  • 2013/5/27 12:48

  • Mamba

  • Moderator

  • Posts: 11366

  • Since: 2004/4/23


It shouldn't, because you have the tables already there. Normally, when the tables already exist, it should check for it, and inform you, but I didn't test it

The easiest and most secure way is to clone it on your local system, and then just copy the files to your server.
Support XOOPS => DONATE
Use 2.5.10 | Docs | Modules | Bugs

5
irmtfan
Re: Updating Cloned Publisher
  • 2013/5/28 2:38

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


Yes.
The current clone system needs this for any update:
1- update the original module (here: publisher) in local
2- create a clone with the same name in your running website.
3- upload the clone files and update in running website.

With changing the clone system to rename of the modules/MODULE it can be done with ease.

Currently i worked on that but it has the least priority in my to do list.

Ones I finished that script based on publisher method, The above can be done on any module which meets the SmartClone standards.

6
chefry
Re: Updating Cloned Publisher
  • 2013/5/28 11:26

  • chefry

  • Home away from home

  • Posts: 1005

  • Since: 2006/10/14


I created the cloned module on my localhost.

Should I install it on the localhost and then copy the files to the server?

7
Mamba
Re: Updating Cloned Publisher
  • 2013/5/28 11:31

  • Mamba

  • Moderator

  • Posts: 11366

  • Since: 2004/4/23


No, just copy the module files
Support XOOPS => DONATE
Use 2.5.10 | Docs | Modules | Bugs

8
chefry
Re: Updating Cloned Publisher
  • 2013/6/6 5:15

  • chefry

  • Home away from home

  • Posts: 1005

  • Since: 2006/10/14


Worked Perfectly!!!

One other question

Right now my main recipe file is called 'publisher' in the URL

the other cloned copies have URL names that make sense (hints, volume, beverages, etc)


I want to clone 'publisher' with the name 'recipes'

How can I import the data from 'publisher' to 'recipes'?

In publisher it doesn't recognize itself (publisher) as a source to import from

From now on, in any website that I use Publisher with, I will install Publisher but make it hidden and only use cloned copies for data so that the URL doesn't say 'publisher'

9
chefry
Re: Updating Cloned Publisher
  • 2013/6/6 5:29

  • chefry

  • Home away from home

  • Posts: 1005

  • Since: 2006/10/14


I updated the clones the way you told me to but now I also notice that they are still showing in the module list of modules to be installed.

All the updated clones show todays date in the list of installed modules

10
Mamba
Re: Updating Cloned Publisher
  • 2013/6/6 21:05

  • Mamba

  • Moderator

  • Posts: 11366

  • Since: 2004/4/23


Quote:
I want to clone 'publisher' with the name 'recipes'
How can I import the data from 'publisher' to 'recipes'?
In publisher it doesn't recognize itself (publisher) as a source to import from

Unfortunately, there is currently not possible to import data from another Publisher module, so you would have to export the data from Publisher with phpMyAdmin and then import it into your Recipe clone
Support XOOPS => DONATE
Use 2.5.10 | Docs | Modules | Bugs

Login

Who's Online

261 user(s) are online (141 user(s) are browsing Support Forums)


Members: 0


Guests: 261


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Mar 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits