It should do that or at least give you a clue where it might cause issues in the errorbox. However jumping to that part is not really possible as due to the recursive usage, it can be everywhere.
londonseo: I know the fun in having to find spintax errors. lol
If you PREVIEW or TEST (depending upon whether it's an article or other content), you may more easily find where, though it may not be so obvious in rarer instances, or if you use more complex, nested spintax.
The text will cut off and be missing, but may pick up later. Or the text may go to spintax, unspun, as output.
You may also find a bracket at the end that shouldn't be there. Anyone know any other possiblities?
Sven: Could a separate utility to just locate mismatched brackets without a pair, instead of being located during spinning and error output to error box, be done?
Comments
If you PREVIEW or TEST (depending upon whether it's an article or other content), you may more easily find where, though it may not be so obvious in rarer instances, or if you use more complex, nested spintax.
The text will cut off and be missing, but may pick up later. Or the text may go to spintax, unspun, as output.
You may also find a bracket at the end that shouldn't be there. Anyone know any other possiblities?
Sven: Could a separate utility to just locate mismatched brackets without a pair, instead of being located during spinning and error output to error box, be done?