Thanks for spotting this bug. It will be fixed in the version on Monday.
NB: How can I turn BBCode on for my post?
We had a spammer problem a couple of years ago. That's why we disabled BBCode. It'd be nice if phpBB had Bayesian spam filtering.
Hi,
I tried to import files to a new version using an xml-file:
<Files dir="commappdata"> <Files dir="mydir1\A"> <File source="F:\path\filename.zip" /> </Files> <Files dir="mydir2\B"> <File source="F:\path\filename.zip" /> </Files></Files>
After the import, I expected to see the following folder structure:
commonappdata mydir1\A mydir2\B
However, I'm getting:commonappdata mydir1\A\mydir2\B
Is that the intended behaviour?
Thanks in advance
Andreas
NB: How can I turn BBCode on for my post?
Thanks for spotting this bug. It will be fixed in the version on Monday.
NB: How can I turn BBCode on for my post?
We had a spammer problem a couple of years ago. That's why we disabled BBCode. It'd be nice if phpBB had Bayesian spam filtering.
wyBuild 2.5.20 is out and this bug has been fixed.
Do you need wyupdate 2.5.20 for this to work? Prior to downloading the update files from the server, my wyupdate client is updated to version 2.5.19 only. Is that the lastest version?
Another remark:I'm opening a wybuild project and I'm clicking on the button "Build updates" afterwards. Afterwards the save button is enabled, indicating that the project file has been changed. Does building the updates really change the underlying project file?
ThanksAndreas
Do you need wyupdate 2.5.20 for this to work? Prior to downloading the update files from the server, my wyupdate client is updated to version 2.5.19 only. Is that the lastest version?
wyUpdate 2.5.19 is still the latest version of wyUpdate (we don't bump the versions to match if nothing has changed). Both the bugs you reported were in wyBuild, not wyUpdate.
Another remark:I'm opening a wybuild project and I'm clicking on the button "Build updates" afterwards. Afterwards the save button is enabled, indicating that the project file has been changed. Does building the updates really change the underlying project file?
Yes. It updates the location of the built update files. That way when you reopen the project file you can upload the updates without rebuilding.
Wyatt > wyUpdate 2.5.19 is still the latest version of wyUpdate (we don't bump the versions to match if nothing Wyatt > has changed). Both the bugs you reported were in wyBuild, not wyUpdate.
I rebuilt the server files using wybuild 2.5.20 and uploaded the files to the server again. I can update to the latest version without problems. However, older files that were removed in the latest version are still not deleted from their according directories.
archaeopteryx> Another remark:archaeopteryx> I'm opening a wybuild project and I'm clicking on the button "Build updates" afterwards. Afterwards archaeopteryx> the save button is enabled, indicating that the project file has been changed. Does building the archaeopteryx> updates really change the underlying project file?
Wyatt > Yes. It updates the location of the built update files. That way when you reopen the project file you can Wyatt > upload the updates without rebuilding.
Seems like the location of the built update files is updated even if it hasn't changed. Would be great if it were changed only if the location was actually altered.
ThanksAndreas
I rebuilt the server files using wybuild 2.5.20 and uploaded the files to the server again. I can update to the latest version without problems. However, older files that were removed in the latest version are still not deleted from their according directories.
This bug has been fixed, but maybe an edge case slipped by. We'll add some extra test cases to try to reproduce what you see.
In the meantime, can you give me a simple example that's not working?
Seems like the location of the built update files is updated even if it hasn't changed. Would be great if it were changed only if the location was actually altered.
That's true. Normally the update filenames have the version numbers in them, though. We'll consider adding this to a future version.
> This bug has been fixed, but maybe an edge case slipped by.> We'll add some extra test cases to try to reproduce what you see.
I played around with it and yes, version 2.5.20 it seems to work fine in all cases.However, to me it Iooks like you may run into trouble when you update from versions that were built with versions prior to version 2.5.20. Its not a big deal, and due to lack of time and availability of the old wybuild versions I won't investigate that any further.
Thanks for fixing that bug in version 2.5.20.
RegardsAndreas
I played around with it and yes, version 2.5.20 it seems to work fine in all cases.However, to me it Iooks like you may run into trouble when you update from versions that were built with versions prior to version 2.5.20.
Right, that's because before v2.5.20 wyBuild was incorrectly comparing versions. (That is, sometimes it skipped a file that needed to be deleted). But you can always rebuild the updates with wyBuild 2.5.20 and you users will be able to update without issue.
I know this is a huge hassle. I apologize. We've written new tests so this issue doesn't pop up in the future.