Spinning – Please Ensure {} Groups Are Properly Closed

We have noticed a problem in a few cases where the spintax that has been submitted has not been properly closed. This seems to happen in extreme cases where there is so much spintax in the source text that it exceeds the maximum field size and gets truncated.

We have extended the size of the input fields to accomodate spintax (they are three times larger) but there are still limits so before submitting your jobs please ensure that your text fields are fully entered and have not been truncated. Note that jobs will only be spun enough to as many versions as there are sites, which for articles is currently 49, so if you’re submitting content designed to be spun to 1000+ unique versions for example, that could be too large for our input fields.

What happens in this case is that the spinning is aborted and the field is submitted as-is, containing the spintax which is obviously not desired.

It should be possible for us to implement a syntax checker that will prevent submission in this case but for the meantime just double check your jobs before submitting.

If you know you have a lot of spintax you may wish to check your existing jobs. You can also fix the problem yourself manually by editing your jobs to see if they are truncated and if so, just remove the last sentence that is cut off. We are going through and doing this for jobs as we find them but if members could fix their own jobs that would save us a little time