Thanks for the reply Phil,
I am now trying to figure out how that file vanishes (actually 'those files'
- my tester has been able to cause this on a few VMs!?)
Any ideas why this could happen (besides tampering?).
These machines may be localized in different languages, too, but my tester
Sorry, here are the two logs.
Setup_AACU_2015-06-30_17-43-54.log
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7600761/Setup_AACU_2015-06-30_17-43-54.log
Setup_AACU_2015-06-30_17-37-01.log
I have a machine where I cannot upgrade my old product to the new version.
It is just on this one machine - it has successfully upgraded on many other
machines of the same version of windows.
Thanks in advance if anyone can tell me why this happens (it is intermittent
even on the same
My VS2010 solution has a bunch of projects in it, and one of them is a WIX
installer. We upgraded perforce recently and now I get a msg like this when
loading the solution / WiX project:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7599070/p4vsFAIL.jpg
My perforce version
I just found the version info for the plugin in VS2010 - it is Microsoft
Visual Studio 2010
P4VS - Perforce Plugin for Visual Studio 2014.2.97.6861
--
View this message in context:
Thanks for looking at this - Downgrading the p4 client cannot be done in this
case because the newer p4 server requires the new one.
BUT! The good news is that I figured it out. You must manually edit the
wixproj file:
replace this:
SccProjectNameSAK/SccProjectName
Is there a way to get something like (In C++) #pragma message(some message)
that I can put in my WiX project file? I want to output in the log the
generated product code each time it is built.
I found warning but I can't get it to output the value of a variable. I
tried a couple of variations
Sorry - I was too impatient... I figured it out ;-) Doh!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/I-swear-I-looked-around-before-asking-about-pragma-message-functionality-tp7598646p7598647.html
Sent from the wix-users mailing list archive
Is there a definition of AdvertiseFlags anywhere that makes sense? I see in
the MSI.H file there are two values - installed per user (1), or installed
per machine (0). But in the registry for the installed product
([HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products]), I am seeing
values
Thanks for the help Nick and Phil!
You guys have helped me a lot here. I am beginning to see the light.
I've got SAME_VERSION set to NOT only-detect because we use the 4th part of
the version number for upgrades. I've got to allow version 1.0.0x150 to
upgrade 1.0.0x149, for example.
I
I apologize ahead of time for this ancient usage example, but this is legacy
code I am afraid to change ;-)
Note that ProductVersion is defined by me and is something like 1.0.0.99 -
and I know MSI disregards the last level of this version info. Also note
that this MSI is installed Per Machine.
Thanks for the replies fellas. Phill is right on - that's the way I do it,
and because I inherited this project and am fearful of making big changes
and screwing it up ;-) it is still done this way. Someday I'll upgrade to
using Burn, too, and get off of the old Wix 3.5.
Now back to the
Thanks for the leads to the vb code - looks promising - and I do still have
the mst files to apply to the base msi using Orca - I was trying to figure
that out before - That helps a lot. I'm going to mess around with the VB
code for a bit.
--
View this message in context:
When I am done building my installer, (which includes a bunch of localization
stuff (which are .mst files embedded into the .msi file))
I'd like to know what the generated ProductCode's are for each .mst file
created in the build step. These files get merged into one .msi file, but I
cant see
This is still a problem. I noticed that this message in the log is the only
occurrence, and when it happens, install fails as described above.MSI (s)
(C0:84) [15:58:39:643]: Using source file security for destination. I'd like
to know just what this message means. MSI has installed the product,
This is happening a lot now with a different installer. It always is a
different file, and the log shows that this is the only entry where the
attempt was made twice twice to verify access (immediately following the
first attempt), and it also is the only entry in the log that has the bit
about
I had a customer report a strange problem and am wondering if anyone can
decipher this message in my log.
The user gets prompted to Retry or Cancel when this problem occurs, and if
they choose to retry, it continues the upgrade apparently without a problem.
After hundreds of files processing
Search for msizap.exe on the msdn website.
On Apr 15, 2013, at 4:03 PM, Marco Tognacci mark...@live.it wrote:
I have think about this problem, if I make a mistake in the setup and for
some reason when I have distributed the setup to customers the setup fail to
uninstall (for example it
Well it worked once in a row for me! (with a very simple msi) .
It is quick and (extremely) dirty for a development VM that you forgot to
take a snapshot of, but I would never say use it where it matters if the
machine is usable afterwards.
--
View this message in context:
I'm surprised that no one has commented on this problem. Either is is such
an advanced question that no one has the answer, but it is such a stupid
question that the answer is obvious.
I'm going with the latter - that this must be the most stupid question asked
all day.
Well, I don't get it,
Thanks Rob,
I used a heat example I found in a thread here - like this:
C:\Program Files (x86)\Windows Installer XML v3.5\bin\heat.exe file
ShellExt.dll -ag -out file.wxs
Should I not do that?
What do you mean to Let the Windows Installer manage the registry keys for
you instead. - how does
Why is this *the right way*? Seems way more complicated - besides - how do I
do that in C++?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Any-ideas-on-how-to-solve-MessageBox-focus-can-be-lost-using-Custom-Action-DLL-tp7584319p7584612.html
We've got a shell extension which hooks into Explorer.exe menus for our
stuff.
It installs ok using a WiX fragment I generated using heat.exe. But when I
try to upgrade it (major upgrade), the files in use dialog displays and
says that it must stop explorer.exe to update the files, and it
Try this - it will keep the messagebox on top of everything.
MessageBox(NULL, LPlease click ok to continue., LSetup messageBox title,
MB_OK | MB_SYSTEMMODAL);
--
View this message in context:
I've got an installer that has to install several hundred files, and it seems
to take a long time to compute the space requirements, especially on an
upgrade.
During this phase, I see in a verbose log that there is a lot of work going
on to just add a backslash to the end of all of the folder
You hit the nail on the head, Michael! I was able to adapt this very easily
to my needs...
You rock! Thanks!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/IUSR-tp6404206p6434276.html
Sent from the wix-users mailing list archive at
I was under the impression that IUSR_USERNAME was a property available from
the WiXIISExtensions. Now that I have researched this a little more, I
realize this is wrong.
I'm just trying to assign specific permissions to a folder for the account
that IIS is running under.
I was hoping to avoid
I'm trying to set permissions on a file like this, using WiX 3.5:
Component Id=MT_PHPLog.log
Guid=0FFF2708-5B65-418A-A4C7-F6FFF5B7ACD9
File Id=MT_PHPLog.log Name=PHPLog.log
Source=$(var.WebFolder)webroot\PHPLog.log
Permission GenericAll=yes
OK, I figured it out - needed to add this (duh):
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-NETWORKSERVICE-tp6179107p6181514.html
Sent from the wix-users mailing list archive at Nabble.com.
Hi,
I have code like this and when I install on XP and win2003, this works fine.
But when I install on win2008R2, I get an error and the install is aborted.
The error is An error occurred while applying security settings. Network
Service is not a valid user or group. This could be a problem
Great! It didn't include my sample code.
Let's try this:
I should also mention that my system has Italian as the localized language,
but not for the user running the install
Sorry, here's the 'real' code:
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-NETWORKSERVICE-tp6179107p6179129.html
Sent
You need to pass in the VS variable value on the WiX project's command
line, by doing something like this:
In the build properties for your WiX project, you can define preprocessor
variables, and there you could specify something like
MYCONFIG=$(Configuration)
Then you can test the MYCONFIG
Is there a way to query the _MSC_VER visual studio preprocessor variable
while building a WiX project using Votive?
We changed the locations of some files when we went to VS2010, but we still
have to build under vs2008, and I'd like to do some conditional fragment
includes based on what version
Well! That's exactly what's going on here. The overlapping keyfile thing is
the problem - After fixing this (by puttting keyfile on the right file (NOT
the component)), the problem is solved!
Phil and Blair: you've both been a big help.
Thanks again for looking at this weird problem (that I
I just bought a copy too - and have devoured the first two chapters. Thanks!
I wish it was around a few months ago!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-book-available-tp5647051p5648913.html
Sent from the wix-users mailing list
Thanks Blair - I wish I was smart enough to find doc like that - direct hit!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/INSTALLDIR-and-Upgrades-reposted-in-correct-forum-tp5635805p5638820.html
Sent from the wix-users mailing list archive at
So on an upgrade, I noticed that some important files were not installed. So
I looked in the log and found these:
MSI (s) (7C:28) [12:04:18:128]: Component: Service_Component; Installed:
Absent; Request: Local; Action: Null
MSI (s) (7C:28) [12:04:18:128]: Component: Admin_Component;
Sorry, looks like I posted too soon.
After trying to use SharedDLLRefCount=yes, my WiX installer still won't
install these components.
I should also note that all of the other components have Action: Local
... and they get installed.
What's going on here?
--
View this message in context:
Thanks for the reply, Phil.
I'm not sure what you mean by migrating feature states, but these two
components probably don't have the same component names as something in the
previous installer version, and they definitely don't have the same
component guids. But neither do the other
Uh Oh. This doesn't sound good...
Here's what I'm doing to determine if I need to upgrade:
Upgrade Id=$(var.UpgradeCode)
UpgradeVersion Minimum=$(var.ProductVersion) OnlyDetect=yes
Property=NEWERVERSIONDETECTED /
UpgradeVersion Minimum=0.0.0 Maximum=$(var.ProductVersion)
Here's two parts of the log... still looking grim...
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n5640249/log.txt
log.txt
Thanks for helping out Phil...
--
View this message in context:
Gladly... here it is. Had to zip it...
Thanks again for trying to help.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n5641073/full.zip
full.zip
--
View this message in context:
Sorry about reposting this; I put it in the wrong forum initially...
My installer allows the user to specify the folder location for the initial
install. But on an upgrade, I'd like to prevent them from changing that
location, so I don't allow them to specify the folder.
I think I understand
Well, after much goofing around, I think UPGRADINGPRODUCTCODE check is
working for what I need. My design is wrong from the start to re-order
removal of existing products... but I will design the next installer with
this method in mind.
Thanks so much for your help Blair... and the great
Hi,
I have 3 components that get installed initially. But when I want to
upgrade, I'd like to leave one component alone - it never needs to be
upgraded. But I do want to upgrade the other two components.
I already can do a successful upgrade, but that removes all of the files
first, then
Hi Blair, and thanks for the response.
What you describe is an advanced functionality that I'm currently incapable
of implementing. I just don't know enough about this stuff to even try that
right now ...
Is there an example of the latter suggestion that you might be able to
provide? (i.e.
Sorry - just found this link to explain RemoveExistingProducts:
http://msdn.microsoft.com/library/aa371197.aspx
I am thinking of trying this, but this says that the RemoveExistingProducts
needs to be scheduled 'between'
the InstallExecute action, or the InstallExecuteAgain action, and the
Well... I was having trouble with PropertyRef on a checkbox control because
you can't do that! I meant to use CheckBoxPropertyRef (which I just learned
about in another post), and that works exactly as advertised. Ugh...
But thanks Bob!
And thanks to Christopher, too. Your suggestion gave me
I have a reason to have a checkbox appear on a different place in the same
dialog, based on a condition. I was trying to use propertyRef to allow both
checkbox controls to use the same property, but I can't get that to work.
Of course if I use the same property for each checkbox, I get a
I have another checkbox - above both of these (let's call it checkbox0) -
that shows/hides based on the TRIAL_VERSION property. This checkbox0 does
not display if TRIAL_VERSION 1.
If trial_version is a 1, then I'd like the checkbox1 to appear under
checkbox0. But if TRIAL_VERSION is not a
Nick!
That works exactly the way I'd like it to... I really appreciate your help!
Thanks!
Greg
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-conditionally-check-uncheck-a-checkbox-tp5539262p5544015.html
Sent from the wix-users mailing
I have a dialog with two check boxes. CB1 and CB2. If CB1 is checked, I'd
like to set CB2 to checked, too. And conversely, I'd like to uncheck CB2 if
CB1 is unchecked.
Control Id=CB1 Type=CheckBox Text=Start [ProductName] services on
exit. Property=LAUNCHSERVICEONEXIT CheckBoxValue=1/
Control
No, I hadn't tried that... but I just did - and it sort of works, but it
isn't what I actually needed. I now have two check boxes that set the same
property (e.g. MyCheckBoxResult).
I'd like CB2 to be checked initially only if CB1 is checked, and vise-versa.
But I would like to allow the user
Sorry for the ambiguity. I'm not asking the right question.
Here's what I'd really like to do:
On entry to this dialog, both CB1 and CB2 should be checked, so I set their
individual properties to 1.
The user can un-check CB2 and it should leave CB1 alone.
If the user un-checks CB1, I'd
How can I tell if a major upgrade is in progress in the UI?
I want to display a special dialog in the upgrade situation...
Thanks
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-check-if-major-upgrade-in-progress-tp5466532p5466532.html
I should add that I'm using this mechanism now, and I test
OLDERVERSIONBEINGUPGRADED, but I wanted to ask if this is the right way,
or is there a different property I can also test?
Upgrade Id=$(var.UpgradeCode)
UpgradeVersion Minimum=$(var.ProductVersion) OnlyDetect=yes
Doh! I figured it out - and I've asked this question before but in a
different way. The answer is:
If you have more than one NewDialog event that has a true condition, the one
with the highest order number will execute, and the others will be ignored.
You need to make your conditions mutually
I found it pretty easy and straightforward using VS2008 to attach to a setup
program awaiting user input from a message box. It was very easy...
This MSND article touches on it -
http://msdn.microsoft.com/en-us/library/aa368264%28VS.85%29.aspx -
just attach to the process that has your
What is the point of the UpgradeGUID?
It appears that it is something independent of the product code - which
means that we could leave the upgrade GUID the same for a variety of
versions which means uninstall anything w/ this upgrade code.
Or, does it mean that we can specify all known
Thanks Blair - That fixed it... it would be cool if your sentence explaining
the problem was easily found or otherwise available in the doc...I was
scratching my head for a long time over this.
--
View this message in context:
I have a next button like this, and it never displays the
MTWebServerConfigDlg dialog.
Control Id=Next Type=PushButton X=236 Y=243 Width=56 Height=17
Default=yes Text=!(loc.WixUINext) TabSkip=no
Publish Event=DoAction Value=CreateMySQLAccount
Order=11/Publish
Publish Event=SpawnDialog
I should also mention that the dialog in question will display if I don't
un-check the CONFIGSMTP check box, i.e. Property CONFIGSMTP = 1...
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Dialog-execution-order-tp5417778p5417804.html
Sent from
Hi,
I need to prompt the user for the location of a file before installing my
software.
I'm disappointed that I couldn't find an example of this ANYWHERE. There
are lots of discussions about using custom browse dialog, but no examples.
If I figure this out, I will publish an example.
I give
Hey Thanks Nick! That was pretty close... This license file won't be
'installed', it will be emailed to the user, so it is possible for the user
to put it anywhere before running setup. So I followed your suggestion to
set the variable correctly, but I set it to C:\, and it is acting
correctly
Did you export the HideCancelButton function correctly (in a def file?)
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Hide-Cancel-button-on-ProgressDlg-with-WiXUI-InstallDir-tp5220745p5222725.html
Sent from the wix-users mailing list archive at
By the way - is this DoAction limitation documented somewhere? It's really
too bad this doesn't work ... waah! (Ok, done whining)...
--
View this message in context:
Thanks Phil, I appreciate that piece of info... Maybe I can use the Message
Method to work around this limitation...
http://msdn.microsoft.com/en-us/library/aa368322(VS.85).aspx
http://msdn.microsoft.com/en-us/library/aa368322(VS.85).aspx
--
View this message in context:
This is clearly another noob question, and I apologize in advance...(I looked
around for the answer, really, but I couldn't find any other dumb questions
like this)...
I'd like to execute a custom action when a dialog is entered. My custom
action is a function in a DLL - to initialize a
Thanks Blair - I figured it out - (with your help!) - I didn't want to modify
the previous dialog (std wix dialog) just to add my 'next' action to it, so
I fumbled around enough with my copy of WixUIInstallDir.wxs and got it to
go... actually very clean/easy once I realized how it works.
--
View
Well, I can't support quiet mode using this installer, partially because of
these bad design decisions, and partially because it wasn't in the original
design and I'm a noob.
I should blog about my experience in the WiX world - it has been a little
confusing, to say the least. It might help
I solved this problem by re-writing part of the code - not sure exactly what
the problem was, but its not a problem anymore.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Dialogs-out-of-order-tp5177864p5190829.html
Sent from the wix-users mailing
Yes, that seems to be the case. Any logging I try to do that works, is in a
custom action, not a DoAction event. The ones that fail are in DoAction
events.
Hmmm. I guess I'll have to keep that in mind.
Thanks for demystifying...
--
View this message in context:
I have a similar problem, and I see this message was ignored by the
community. Maybe it is a stupid question? I dunno - but I have the problem
too.
I noticed my MSIHANDLE is one ('1') before installation of the files. AFter
the files are installed, the MSIHANDLE is eight ('8').
Before
Thanks for the reply, Blair.
Yeah, I just tried that for the heck of it... I would not ever do that in
production...
But the problem remains... I cannot log something late in the install
process...
--
View this message in context:
Hi Sascha - Thanks for the example code.
I understand the out-of-scope handle problem, and I don't save one and use
it for something...I just mentioned that in the previous post to see if it
made a difference during debug.
My code does work, until after install. I can log all day, but not
WARNING
Another NOOB alert...
/WARNING
After all of my files get installed, I need to prompt for some additional
configuration information.
I created a custom dialog to do this. It has a couple check boxes on it.
I would like to NOT have this dialog run at all if the user is removing the
More NOOB stuff follows:
The following code doesn't run in the order that I would have expected,
based on the Order= parameters.
I would like to display the ConfigSQLDlg before the ConfigSMTPDlg, but this
actually
happens in the reverse order... SMTP is first, then SQL.
Note that the
Show Dialog=ExtraConfigDlg OnExit=success![CDATA[(REMOVE ALL) AND
NOT Installed]]/Show
The AND NOT INSTALLED clause solved that problem - thanks Pally...
The reason I can't ask the configuration questions earlier in the install
process is that the installer installs a needed file. After this
Actually, being such a NOOB, I can't see the connection between this post and
the previous one... they do seem to be separate problems to me...
But that said, I'll review and continue this thread if I can't figure it
out.
Thanks again!
--
View this message in context:
Hi Pally (et. al.),
I don't see how this post and the other (previous on from me) are related,
so this question still stands...
TIA
Greg
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Dialogs-out-of-order-tp5177864p5178373.html
Sent from the
What's stopping you asking the user questions in the InstallUISequence
running the DLL function in the InstallExecuteSequence as is standard
practice? Your custom action doesn't need to run immediately as soon as
you gather information from the user, you can still schedule it after
InstallFiles
Can I do that? I'd like to spawn a different dialog from a spawned dialog.
I looked around - this Q must have been asked before - but I couldn't find
it.
TIA
Greg
--
View this message in context:
I created a custom dialog and stuck the forward and backward links in my copy
of WixUI_InstallDir.wxs:
Publish Dialog=MyConfigDlg Control=Back Event=NewDialog
Value=InstallDirDlg Order=1NOT Installed/Publish
Publish Dialog=MyConfigDlg Control=Next Event=NewDialog
Thanks for the quick response, Pally.
That is the problem - I was hoping to not have to add an extra button. I
couldn't figure out how to check everything before the user clicks the next
button...
Hmmm.
Any other ideas?
Thanks again
Greg
--
View this message in context:
Hmmm. I could give that a try...
My dialog has 4 edit controls on it that need to be filled in by the user,
and then parsed by the DLL,
Like you said, maybe another 'validate' button is the best way. I'll try a
few things and report back.
Thanks again...
--
View this message in context:
Perfect Mike! That's what I was looking for... It works GREAT! Thanks!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/NEXT-button-behavior-tp5163545p5166022.html
Sent from the wix-users mailing list archive at Nabble.com.
Ugh. I uninstalled/reinstalled wix 30 and still same problem. I eventually
figured out that I had to do a devenv /resetskippkgs at the command line,
and it all works again now.
Thanks for your help everyone!
--
View this message in context:
I see that the source tree moved from SourceForge to codeplex YESTERDAY. But
on the 3.5 stuff is on codeplex. Where did the 'stable' release of 3.0 go?
Today I couldn't load my wix project in VS2008 for some reason. I got a
message like this:
Thanks Neil - I found it.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-What-happened-to-3-0-tp5151154p5151179.html
Sent from the wix-users mailing list archive at Nabble.com.
Somehow I broke my VS2008 project and I can't load my wixproj any more. I'm
getting the following error:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n5151101/error.jpg
Reinstalling 3.0 didn't help. Any suggestions on how to fix this?
--
View this message in context:
Thanks! That worked!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Starting-a-service-conditionally-after-InstallInitialize-tp5135712p5139702.html
Sent from the wix-users mailing list archive at Nabble.com.
Hello group -
I'm still a NOOB and I'm trying to start a service conditionally after
everyting is installed, and I modified the ExitDialog for WiX to show a
check box which sets the value for LAUNCHAPPONEXIT to 1 if the user checked
the checkbox.
This almost works, except I get this message in
I'm trying to use WixUI_InstallDir as my UI, and when I do, and compile it,
and run it, I get the following message in the MSI log:
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2343. The
arguments are:
Aw man! Pally! You rock!
Thanks for the quick response - That fixed it!
I was confused by the tutorial here:
http://www.tramontana.co.hu/wix/lesson2.php
I put Property Id=WIXUI_INSTALLDIR Value=TOP_LEVEL_DIR /
because I saw in this tutorial that it was needed if I used
WixUI_InstallDir!
OH! Duh! (Sheesh!)
Thanks - that makes sense.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Trying-to-keep-it-simple-WixUI-InstallDir-error-2343-tp5094719p5095087.html
Sent from the wix-users mailing list archive at Nabble.com.
Well it seems like that should work... I didn't see that in the example you
linked to?...hmmm.
And now we have this, too:
http://www.winsupersite.com/server/whs_vail_preview.asp
WHS Based on Win2008R2. So the version info is changing.
--
View this message in context:
I'm running WHS v5.2 build 3790.srv03_sp2_gdr.100216-1301 : Service Pack 2.
I think you need to check one more bit. The example you linked to
previously doesn't check the suite name.
I jammed the folowing code into a dll, and I call that, and it works
correctly between 2003 and WHS.
bool
Thanks for the hint, Bob. I ran the installer and produced a log, but I
don't see anything obviously wrong in there. (But I'm a noob). I ran this
on a WH Server, using V3.0.5419 of WiX, and it prevents me from installing.
Maybe you could take a quick look? I'd appreciate it...
I included
Bump?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/PropertyRef-WIX-SUITE-WH-SERVER-tp4933515p4947530.html
Sent from the wix-users mailing list archive at Nabble.com.
--
100 matches
Mail list logo
