I'm a noob. I had the same problem. I discovered in CB if you go into Admin_Menu>>Components>>Community_Builder>>Tools, one of the options will be "Check Community Builder Database". This runs a series of tests and will report anomalies in your database (and also the directory structures). In my case, I had read all of the posts about opening up permissions on the images directory but, being new, I was looking at the wrong directory. The above check discovered that the web server could not read/write to the desired directory. In fact, it the directory didn't even exist so I suspect the installed couldn't create but moved on. So, I created the problem dir reported by the above tester then I opened permissions and it worked. So, the lesson is not to be fooled by chmod'ing the wrong dir. Use the checker and it will present the full path of the offending directory and then it's quite simple to fix.
I'm a noob. I had the same problem. I discovered in CB if you go into Admin_Menu>>Components>>Community_Builder>>Tools, one of the options will be "Check Community Builder Database". This runs a series of tests and will report anomalies in your database (and also the directory structures). In my case, I had read all of the posts about opening up permissions on the images directory but, being new, I was looking at the wrong directory. The above check discovered that the web server could not read/write to the desired directory. In fact, it the directory didn't even exist so I suspect the installed couldn't create but moved on. So, I created the problem dir reported by the above tester then I opened permissions and it worked. So, the lesson is not to be fooled by chmod'ing the wrong dir. Use the checker and it will present the full path of the offending directory and then it's quite simple to fix.
I'm a noob. I had the same problem. I discovered in CB if you go into Admin_Menu>>Components>>Community_Builder>>Tools, one of the options will be "Check Community Builder Database". This runs a series of tests and will report anomalies in your database (and also the directory structures). In my case, I had read all of the posts about opening up permissions on the images directory but, being new, I was looking at the wrong directory. The above check discovered that the web server could not read/write to the desired directory. In fact, it the directory didn't even exist so I suspect the installed couldn't create but moved on. So, I created the problem dir reported by the above tester then I opened permissions and it worked. So, the lesson is not to be fooled by chmod'ing the wrong dir. Use the checker and it will present the full path of the offending directory and then it's quite simple to fix.