Content Blocks breaking when they have more than 2 images

Permalink
Hey Everyone,
So, I had a website pretty much finished, but we were having troubles with a slow godaddy server. So godaddy moved the site to a different server, thus breaking the Concrete install.

So I copied out all of the "files" folders and backed up the database, and did a fresh install, put all the "files" folders back, and restored the database after a clean install.
I had some troubles with the add-on, since the database thought they were installed but really weren't, so I had to delete those entries manually, and reinstall, no problem. Here is the problem, ever since this re-install, a content blog that gets more than 2 images, seems to break. It breaks everything, my CSS, the content block, everything. I can put all the text in, have all the headings defined, and it works great, I put in 1 images, it still works. 2 images, still works, a 3rd images results in something like a div tag no being closed, I am not sure what happen, but all the content in that block doesn't show up and any div I have after that don't show up either.

Has anyone had this problem before?

The website ishttp://www.upharts.org. You can see the results of this broken block on the events(this page has all text, but no images as of now, so it is kind of working, so you can see what the layout should look like) and programs pages(this on is broken, and you can see how it messes with my divs after that block).

danielromney
 
danielromney replied on at Permalink Best Answer Reply
danielromney
So I figured it out. I tried to go in and "rescan" some of the images I noticed it messing up on, and the ones that threw out the "Could not scan...... because of memory issues (this is paraphrased of course)" I downloaded, down-sampled a little and re-uploaded, and they worked. So I found a temporary fix.
danielromney replied on at Permalink Reply
danielromney
And to expound on this a little, I did run into some issues with rescanning the images, running into a memory error, but that was easily fixed doing a little searching and editing my php5.ini file to allocate more memory.

This website stores cookies on your computer. These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media. To find out more about the cookies we use, see our Privacy Policy.