Where is SeedCode Subscribe?
SCSubscribe2.WhereIsSubscribe History
Show minor edits - Show changes to output
Changed lines 17-19 from:
-> You only need to edit that path if you've put it [[Remote PHP Deployments | somewhere else]].
-> Note that if you seegreen check mark AND the version number of the engine, you'll know you've put it in the right place and SeedCode Subscribe can see it.
-> Note that if you see
to:
-> If your web server and FileMaker Server are on different machines, enter the FileMaker Server's address in the "configuration.ini" file, which can be found in the "seedcode_subscribe_engine" folder. Open the configuration.ini file in a text editor and change "localhost" to your FileMaker Server's address, then uncomment that line by removing the semicolon at the front of that line.
Changed line 13 from:
-> When you've purchased SeedCode Subscribe and installed the seedcode_subscribe_engine folder on your own FileMaker Server, just enter that address. By default SeedCode Subscribe assumes your web server and your FileMaker Server are on the same machine.
to:
-> When you've purchased SeedCode Subscribe and installed the seedcode_subscribe_engine folder on your own FileMaker Server, enter the path to that folder. By default, we assume your FileMaker Server is on the same machine.
Changed line 7 from:
-> When using our public engine, we just need to know where your FileMaker Server is.
to:
-> When using our public engine, just enter the address of your FileMaker Server.
Changed lines 3-4 from:
!!What is the correct Location for SeedCode Subscribe
to:
!!What is the Correct Location for SeedCode Subscribe?
Changed lines 7-8 from:
-> You don't need to worry about this field when using our public engine: Subscribe knows where that is and where the seedcode_subscribe_engine folder is installed on it:
to:
-> When using our public engine, we just need to know where your FileMaker Server is.
Changed line 13 from:
-> When you've purchased SeedCode Subscribe and installed the engine on your own FileMaker Server, you just need to tell the app where it lives. By default the app assumes it's on your FileMaker Server and will enter a path for you like this:
to:
-> When you've purchased SeedCode Subscribe and installed the seedcode_subscribe_engine folder on your own FileMaker Server, just enter that address. By default SeedCode Subscribe assumes your web server and your FileMaker Server are on the same machine.
Changed lines 9-10 from:
Attach:location1.jpg
to:
Attach:location1.png
Changed line 15 from:
Attach:location2.jpg
to:
Attach:location2.png
Changed lines 5-6 from:
'''When Using the Demo Server'''
to:
'''When Using the Public Engine'''
Changed lines 9-10 from:
to:
Attach:location1.jpg
Changed line 15 from:
to:
Attach:location2.jpg
Changed lines 7-8 from:
-> You don't need to worry about this field when using our demo server: Subscribe knows where that is and where the seedcode_subscribe_engine is installed on it:
to:
-> You don't need to worry about this field when using our public engine: Subscribe knows where that is and where the seedcode_subscribe_engine folder is installed on it:
Changed lines 13-14 from:
-> When you've purchased SeedCode Subscribe and installed the engine on your own FileMaker Server, you just need to tell the app where it lives. By default the app assumes its on your FileMaker Sever and will enter a path for you like this:
to:
-> When you've purchased SeedCode Subscribe and installed the engine on your own FileMaker Server, you just need to tell the app where it lives. By default the app assumes it's on your FileMaker Server and will enter a path for you like this:
Changed lines 17-19 from:
-> You only need to correct that path if you've put it [[Remote PHP Deployments | somewhere else]].
-> Note that if you see the green check mark AND the version number of the engine, you'll know you've put it in the right place andthe URL Builder can see it.
-> Note that if you see the green check mark AND the version number of the engine, you'll know you've put it in the right place and
to:
-> You only need to edit that path if you've put it [[Remote PHP Deployments | somewhere else]].
-> Note that if you see the green check mark AND the version number of the engine, you'll know you've put it in the right place and SeedCode Subscribe can see it.
-> Note that if you see the green check mark AND the version number of the engine, you'll know you've put it in the right place and SeedCode Subscribe can see it.
Changed lines 9-10 from:
Attach:location1.jpg
to:
%center% %width=400 newwin% [[Attach:location1.jpg | Attach:location1.jpg]]
Changed line 15 from:
Attach:location2.jpg
to:
%center% %width=400 newwin% [[Attach:location2.jpg | Attach:location2.jpg]]
Changed line 15 from:
Attach:[[http:// | link text]]
to:
Attach:location2.jpg
Changed lines 13-21 from:
to:
-> When you've purchased SeedCode Subscribe and installed the engine on your own FileMaker Server, you just need to tell the app where it lives. By default the app assumes its on your FileMaker Sever and will enter a path for you like this:
Attach:[[http:// | link text]]
-> You only need to correct that path if you've put it [[Remote PHP Deployments | somewhere else]].
-> Note that if you see the green check mark AND the version number of the engine, you'll know you've put it in the right place and the URL Builder can see it.
-> Don't see a green check mark or version number here? Check out our [[troubleshooting]] suggestions.
Attach:[[http:// | link text]]
-> You only need to correct that path if you've put it [[Remote PHP Deployments | somewhere else]].
-> Note that if you see the green check mark AND the version number of the engine, you'll know you've put it in the right place and the URL Builder can see it.
-> Don't see a green check mark or version number here? Check out our [[troubleshooting]] suggestions.
Changed line 9 from:
Attach:file.ext | link text
to:
Attach:location1.jpg
Added lines 1-13:
(:title Where is SeedCode Subscribe?:)
!!What is the correct Location for SeedCode Subscribe
'''When Using the Demo Server'''
-> You don't need to worry about this field when using our demo server: Subscribe knows where that is and where the seedcode_subscribe_engine is installed on it:
Attach:file.ext | link text
'''When Using Your Own Installation of the Subscribe Engine'''
czvs
!!What is the correct Location for SeedCode Subscribe
'''When Using the Demo Server'''
-> You don't need to worry about this field when using our demo server: Subscribe knows where that is and where the seedcode_subscribe_engine is installed on it:
Attach:file.ext | link text
'''When Using Your Own Installation of the Subscribe Engine'''
czvs
