Looking at previous posts at new RW updates, this appears to be a bug that happens at RW update time.
In RW 7.1.0, in a file that was begun in the previous RW version, I am getting this error whenever I try to publish the site. Here is the detailed message:
-__NSCFString characterAtIndex:: Range or index out of bounds : Range or index out of bounds
I updated to RW 7.1.1 today. It crashes one second after I press PUBLISH. It happens on projects I published successfully by RW 7.1.0 on last days. Restarted MB. I cannot publish anymore. Please Help!
The problem seems to be that Rapidweaver thinks the Foundation Theme is missing. And it is occurring not only on this file, but on new files I generate. I am getting the âExceptionâ message and file crashing when I try to go to Master Styles in this file, and any new file I try to open. And am getting messages on opening files that âFoundation Theme is Missingâ and Rapidweaver will therefore install Foundation. When Master Styles does open the area it opens is blank except for a dropdown with default theme chosen but no other options in the dropdown.
I see here that this issue is reported as having been solved with 7.1.3 but Iâm experiencing the same issue on 7.1.5 with one project file only.
Steps to reproduce: Clicking âPublishâ results in âUnable to exportâ with the error: â-[__NSCFString characterAtIndex:]: Range or index out of bounds.â
Steps taken so far trying to resolve:
Tried publishing one page only.
Tried restarting Rapidweaver.
Ensured that all stacks and plug-ins were up to date.
Tried removing Pluskit.
Tried reinstalling latest Foundation theme.
I am able to publish a small non-Foundation themed site but not a biggish Foundation themed site.
Any help you can offer is greatly appreciated.
Christopher
Update: Same issue as above with 7.1.6 and 7.1.7
Update 2: Downgraded to 7.1.3. Same issue.
Using RW 7.1.5 I am getting an âexception while exporting siteâ error message with the following details: -[NSURL initFileURLWithPath:] nil string parameter.
Anyone have suggestions as to where I need to to go from here?
Weâre looking into this issue now, but it appears itâs caused by the âMinify CSS and Javascriptâ option in RW in conjunction with using the Foundation theme (cc @joeworkman).
For now just switch off the âMinify CSS and Javascriptâ option under the advanced general settings. and your site should preview and export just fine.
If itâs an RW issue, weâll get an updated shipped asap.
Minify CSS still needs to be turned off with 7.1.7 on Sierra, otherwise there is still the error âindex out of boundsâ when publishing.
Will there be any release to finally fix that?
Same issue as above. Cannot export any site, Iâve unchecked Minify CSS and Javascript and also tried older versions of Rapid Weaver none of which work.
I donât get any error message on screen apart from âRapid Weaver closed unexpectedlyâ send report etcâŚ
Rapid Weaver Version: 7.1.7 (18375)
MacOS: Sierra, Version 10.12.1
I just had this issue with in RW 7.5.1.
I have a fully published operational website that I only made some tweaks to last night and now it wonât publish. Minify CSS was already turned off, so that solution did not resolve anything.
I have read the thread and I am trying to publish one page at a time. This works. BUT, after I went down the whole list of pages and finally got to the Sitemap page, when I published that, it put blue dots on all the pages I just tediously uploaded one at a time and now I am doing that process all over again. Anyone else doing this, I suggest you start with the Sitemap page first before uploading every other page.
SIDENOTE: Why does the contact page have 158 elements that have to be uploaded when all my other pages average around 20 elements? That seems excessive for such a simple form page.
After doing publishing each page seperately, I saved the file, then made a copy. I made minor changes on the copy and did a regular full publish of the site and it seemed to work normal.
I also use Meta Mate stack. Making a change in Meta Mate prior to publishing last night might have caused this error, but I am not sure. I just made a change in on a page in Meta Mate which affected all the pages, causing me to do a new full upload, but no problems. The full site uploaded.