I'm getting ready to do the jump to the 5.1 series, couple questions as I test things here.
I never did get the clone tool to work properly. Numerous attempts, It initiated and appeared to continously time out.
After each attempt, I'd have a clone directory created with a few wsn directories inside but no files. Then it appeared to start over and recreated another clone directory inside the existing clone directory and begin the process again.
In the end I would end up with 7 or 8 instances of the clone directory and it's contents all inside each other.
I gave up on that and created my own clone.
My question is assuming the clone tool would have worked properly, what does it do with the database? Does it create a clone database?....Or are there no database changes in the 5.1 series?
I dont want to initiate the jump to 5.1 on my clone until I know it's not going to make database changes I cant revert back to.
The clone tool copies the entire database to new tables that have a clone_ tables prefix (as reflected in the modified config.php). I guess that's why it times out for you, if your database is large.
I dont want to initiate the jump to 5.1 on my clone until I know it's not going to make database changes I cant revert back to.
Why's that? It's a clone, the point of it is that if it goes wrong you can just trash it.
There are database changes all the time, within series too. The database changes aren't the dangerous part (templates and particular features you're relying on are).
I meant to say I didnt want to switch to 5.1 and not be able to revert back, meaning without a clone.
But you answered my question, it creates additional tables in the DB for the clone to use.
So theoretically I can either create my own SQL dump and create the clone tables myself, or just recreate the entire database. Make the appropriate adjustments in config.php and I'm good to go.
It said it couldn't find upgrade.php and to run it manually. So once I had done that I was presented with close to 70 different manual template changes. Most of which I couldn't search out because the surrounding code didn't exist.
After making the edits that were possible, I went back out front to observe the damage, and was told the page did not not exist.
Tried running upgrade.php again, but this time I cut all ties and let it upgrade everything. Figured I'd just start over and rebuild all my templates from scratch again. It didn't like that, templateschema.wsn not found.
So once I had done that I was presented with close to 70 different manual template changes.
There are no template changes listed to make between 5.0 and 5.1 when the autoupgrade runs successfully. The problem is that the autoupgrade didn't complete, and the manual upgrade isn't set to work the same (it lists changes like it was an in-series upgrade) -- I'll have that fixed in 5.0.2 so that, at worst, the manual upgrade will work the same as the autoupgrade.
Tried running upgrade.php again, but this time I cut all ties and let it upgrade everything. Figured I'd just start over and rebuild all my templates from scratch again.
Not necessary, the intent is to support 5.0 templates with no changes, though they'll lack some of the 5.1 features.
It didn't like that, templateschema.wsn not found.
That'll happen when you run an upgrade a second time when you're already on the latest version, because it can't know what you want to upgrade templates from anymore.
I only have 183 links in my links directory, the database isn't that large.
Okay, I cloned a site with a 1GB database, so size isn't the issue here.
So what causes the clone tool to create all these recursive copies until it literally passes out cold?
What's in the clone url and clone path boxes on the clone utility page? Could it have the pre-filled path wrong?
I've dumped the clone directory and tried starting over several times, looking for some sort of breaking point, or consistency, and it doesn't even finish copying the directories, before it begins another clone session inside the now cloned "clone" directory.
The path there is missing a trailing slash compared to what I get, but removing the slash doesn't cause me problems so that doesn't seem to be the issue.
it doesn't even finish copying the directories, before it begins another clone session inside the now cloned "clone" directory.
Yes, it seems to be something going on in the recursivecopy function. Outside of a symlink pointing back to a directory above itself, though, I can't imagine what could be a problem there. Presumably you'd be aware if you had any sort of special filesystem redirectors beneath the WSN install directory.
I get it now. Because you're installed at public_html, the clone is being created inside the directory that's being cloned, causing it to repeat. Added a check to avoid copying the clone directory itself.
With that fixed, the fact that you have so many different other scripts as subdirectories of WSN and so many random files still causes it to timeout.
Also, in 5.0 you have to add lines on the SEO page to make the clone directory accessible -- along with any other subdirectories of WSN that should be accessible. (5.1 handles that automatically.)
I'll work on a new clone utility that excludes other scripts.
On my setup, it's cloning all the directories, and the only file cloned is config.php
The config.php is empty though.
I copied all my files over and I too created my own config.php for the cloned version, and created my own .htaccess file for it as well, which got it going.
The only thing that strikes me odd beyond that is, and maybe there are no template changes for displaylinks.php, but the index file clearly shows the conversion. Clicking on a catagory and viewing the links seemed to have remained the same, including the dark theme css. I had to go back and install the dark theme to get the index file to use it.
With all that said....I'm liking what I see so far. Hopefully I can be completely converted with all my template modifications before the weekend is over. I'm choosing NOT to keep modified templates, cause I want to see and possibly use the new features.
finsandfur wrote: maybe there are no template changes for displaylinks.php, but the index file clearly shows the conversion. Clicking on a catagory and viewing the links seemed to have remained the same, including the dark theme css. I had to go back and install the dark theme to get the index file to use it.
On upgrade, new stylesheet elements since the version you were on are added from the default stylesheet -- thus they'll turn white until edited (they're placed at the end of the stylesheet). I don't currently have a way for it to know where it was downloaded from as a custom style and get new style elements from there. It'd be nice to have but it's not a top priority.
0/5
1
2
3
4
5
Sorry, you don't have permission to post posts. Log in, or register if you haven't yet.
Comments on 5.1 series - clone testing
Forum Regular
Usergroup: Customer
Joined: Apr 18, 2006
Total Topics: 28
Total Comments: 103
Posted Sep 19, 2009 - 7:57 AM:
I'm getting ready to do the jump to the 5.1 series, couple questions as I test things here.
I never did get the clone tool to work properly. Numerous attempts, It initiated and appeared to continously time out.
After each attempt, I'd have a clone directory created with a few wsn directories inside but no files. Then it appeared to start over and recreated another clone directory inside the existing clone directory and begin the process again.
In the end I would end up with 7 or 8 instances of the clone directory and it's contents all inside each other.
I gave up on that and created my own clone.
My question is assuming the clone tool would have worked properly, what does it do with the database? Does it create a clone database?....Or are there no database changes in the 5.1 series?
I dont want to initiate the jump to 5.1 on my clone until I know it's not going to make database changes I cant revert back to.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
The clone tool copies the entire database to new tables that have a clone_ tables prefix (as reflected in the modified config.php). I guess that's why it times out for you, if your database is large.
I dont want to initiate the jump to 5.1 on my clone until I know it's not going to make database changes I cant revert back to.
Why's that? It's a clone, the point of it is that if it goes wrong you can just trash it.
There are database changes all the time, within series too. The database changes aren't the dangerous part (templates and particular features you're relying on are).
Forum Regular
Usergroup: Customer
Joined: Apr 18, 2006
Total Topics: 28
Total Comments: 103
I worded that last sentence wrong.
I meant to say I didnt want to switch to 5.1 and not be able to revert back, meaning without a clone.
But you answered my question, it creates additional tables in the DB for the clone to use.
So theoretically I can either create my own SQL dump and create the clone tables myself, or just recreate the entire database. Make the appropriate adjustments in config.php and I'm good to go.
I'm going to give it a whirl
Forum Regular
Usergroup: Customer
Joined: Apr 18, 2006
Total Topics: 28
Total Comments: 103
Not good.
It said it couldn't find upgrade.php and to run it manually. So once I had done that I was presented with close to 70 different manual template changes. Most of which I couldn't search out because the surrounding code didn't exist.
After making the edits that were possible, I went back out front to observe the damage, and was told the page did not not exist.
Tried running upgrade.php again, but this time I cut all ties and let it upgrade everything. Figured I'd just start over and rebuild all my templates from scratch again. It didn't like that, templateschema.wsn not found.
Back out front page does not exist again.
Forum Regular
Usergroup: Customer
Joined: Apr 18, 2006
Total Topics: 28
Total Comments: 103
So what causes the clone tool to create all these recursive copies until it literally passes out cold?
I only have 183 links in my links directory, the database isn't that large.
This is where it continously buckles it's knees and drops to the floor. /public_html/clone/clone/clone/clone/clone/clone/clone/clone
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
So once I had done that I was presented with close to 70 different manual template changes.
There are no template changes listed to make between 5.0 and 5.1 when the autoupgrade runs successfully. The problem is that the autoupgrade didn't complete, and the manual upgrade isn't set to work the same (it lists changes like it was an in-series upgrade) -- I'll have that fixed in 5.0.2 so that, at worst, the manual upgrade will work the same as the autoupgrade.
Tried running upgrade.php again, but this time I cut all ties and let it upgrade everything. Figured I'd just start over and rebuild all my templates from scratch again.
Not necessary, the intent is to support 5.0 templates with no changes, though they'll lack some of the 5.1 features.
It didn't like that, templateschema.wsn not found.
That'll happen when you run an upgrade a second time when you're already on the latest version, because it can't know what you want to upgrade templates from anymore.
I only have 183 links in my links directory, the database isn't that large.
Okay, I cloned a site with a 1GB database, so size isn't the issue here.
So what causes the clone tool to create all these recursive copies until it literally passes out cold?
What's in the clone url and clone path boxes on the clone utility page? Could it have the pre-filled path wrong?
Forum Regular
Usergroup: Customer
Joined: Apr 18, 2006
Total Topics: 28
Total Comments: 103
I've got WSN running in site root and the prefilled paths are;
I've dumped the clone directory and tried starting over several times, looking for some sort of breaking point, or consistency, and it doesn't even finish copying the directories, before it begins another clone session inside the now cloned "clone" directory.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
The path there is missing a trailing slash compared to what I get, but removing the slash doesn't cause me problems so that doesn't seem to be the issue.
I could step through it on your server to find out: http://www.wsnlinks.com/inspection.html
it doesn't even finish copying the directories, before it begins another clone session inside the now cloned "clone" directory.
Yes, it seems to be something going on in the recursivecopy function. Outside of a symlink pointing back to a directory above itself, though, I can't imagine what could be a problem there. Presumably you'd be aware if you had any sort of special filesystem redirectors beneath the WSN install directory.
Forum Regular
Usergroup: Customer
Joined: Apr 18, 2006
Total Topics: 28
Total Comments: 103
Nope, no redirects on that domain at all.
I'll send you some info, and you can take a look when you get time, and see if you step through it and pin it down.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
I get it now. Because you're installed at public_html, the clone is being created inside the directory that's being cloned, causing it to repeat. Added a check to avoid copying the clone directory itself.
With that fixed, the fact that you have so many different other scripts as subdirectories of WSN and so many random files still causes it to timeout.
Also, in 5.0 you have to add lines on the SEO page to make the clone directory accessible -- along with any other subdirectories of WSN that should be accessible. (5.1 handles that automatically.)
I'll work on a new clone utility that excludes other scripts.
Forum Regular
Usergroup: Customer
Joined: Apr 18, 2006
Total Topics: 28
Total Comments: 103
Sounds good Paul
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
New clone utility done for 5.0.71 / 5.1.3.
Forum Regular
Usergroup: Customer
Joined: Apr 18, 2006
Total Topics: 28
Total Comments: 103
On my setup, it's cloning all the directories, and the only file cloned is config.php
The config.php is empty though.
I copied all my files over and I too created my own config.php for the cloned version, and created my own .htaccess file for it as well, which got it going.
The only thing that strikes me odd beyond that is, and maybe there are no template changes for displaylinks.php, but the index file clearly shows the conversion. Clicking on a catagory and viewing the links seemed to have remained the same, including the dark theme css. I had to go back and install the dark theme to get the index file to use it.
With all that said....I'm liking what I see so far. Hopefully I can be completely converted with all my template modifications before the weekend is over. I'm choosing NOT to keep modified templates, cause I want to see and possibly use the new features.
Forum Regular
Usergroup: Customer
Joined: Apr 18, 2006
Total Topics: 28
Total Comments: 103
All switched over.
Looks good, runs smooth. Thanks Paul.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
maybe there are no template changes for displaylinks.php, but the index file clearly shows the conversion. Clicking on a catagory and viewing the links seemed to have remained the same, including the dark theme css. I had to go back and install the dark theme to get the index file to use it.
On upgrade, new stylesheet elements since the version you were on are added from the default stylesheet -- thus they'll turn white until edited (they're placed at the end of the stylesheet). I don't currently have a way for it to know where it was downloaded from as a custom style and get new style elements from there. It'd be nice to have but it's not a top priority.