Thanks for taking care and keeping your eye on all issues.
Unfortunately, we got a corrupted header and changing settings won’t help.
See a production site, running CC 126.96.36.199
and a backup site, CC 11.1 plus WP 3.5.1
There is just a piece of the header.
All CC settings are the same ( I was importing the database and then double-checked them).
Please look into the matter.
Thanks again for your great efforts.
I took the latest CC 1.11 release ( January 24) from github, hoping that my issue would be solved.
Ironically, the header appears more in comparison with January 16 CC 1.11 release, just like a moon appears, but not a full moon yet. 🙂
We have a hope that you will look into the matter.
By the way, when I import the database from the production site to restore the backup site, WP reads that CC theme not found.
After changing CC folder from “Custom-Community-master” to “custom-community” I am able to run the CC 1.11
Thanks again for your business.
thanks for all the feedback!
regarding header: it appears to me that your header height could be set to 658px?
and if so, it also looks like you wrote it with “px” at the end, so it will result in “658pxpx”, and the CSS will do nothing then..
-> could you check if this is true?
then, it would be great if you describe exactly what is left now. as exactly as possible and case per case, so we can analyze, work down and fix the issues.
as you updated from CC 188.8.131.52, it might be you have to rework a few things, if you have a lot of custom CSS or child theme, there might be some things old already or some CSS not working anymore. depends on the level of customization.
thanks for your help and reporting,
we do the best to get all bugs squished as quickly as possible 😉
1. You are right as always. 🙂 I removed ‘px’ and adjusted its number. The header is okay.
2. It seems that there is only one problem left. Please look at the backup site’s sidebar. There is no room or too little space between sidebar’s dark-blue headers and their content underneath. “RSS” is together with the RSS icon image, the same with the following “Bienvenidos a Necesito de Todos” and its content, starting with “Comenzamos a notar que el sistema que hemos…” and so on down to the bottom.
That’s all. Thanks for caring.
Regarding your suggestions that there are some custom CSS, I don’t think so. I didn’t start supporting this site from the very beginning, I took it over one year ago when there was the previous CC 1.8.x (don’t remember its version). I have upgraded it to the CC 184.108.40.206 by overwriting the theme without custom tweaks, as long as as can remember.
Thanks again for your great support!
Hi Mike, sounds great!
Thanks for the nice 2 links showing the difference in your widgets. I was able to find and fix the bug immediately 🙂
Pushed to Github already.
More fixes are just on the way..
Have a great day, Konrad
Thanks again for taking care. The widgets look fine.
I was making the final tests before upgrading the production site.
Guess what? I bumped into featured images failure. All 4 small images, something like 250×170 px, which I used for testing, become stretched. See the backup site.
But the most terrifying thing is that I got:
“Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, firstname.lastname@example.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.”
while working on featured images. That problems seems steady, it happens at least five times and I was waiting for the server to come back alive. I was able to set only two featured images before giving up.
In the end, I gave up and switched to the default “Twenty Twelve” WP theme and set another two featured images. There was no Internal Server Error message while I was working on Twenty Twelve.
Listen up, I will set up an out-of-the-box WP 3.5.1 and your latest CC version. No plugins, just a vanilla plain install. I would try to set featured images there and let you know whether Internal Server Error message comes or not.
By the way, I have checked logs for the errors, there was nothing for January 28.
I will be in touch 🙂
Take care, Konrad.
Thanks again for all your efforts.
the images are set to auto-fit now, so if you have too small images there will be no space but images will get stretched. if you make them fit they will not be stretched.
** But for the next update there will come a new feature for the slider so you can choose if you want to enable image auto fit mode or not.
See Link at Github here: https://github.com/Themekraft/Custom-Community/issues/78
Regarding the internal server error bug, please let us know if you observe any strange behaviours! thanks a lot for your help, next update(s) are on the way with a lot of fixes and cool new stuff.
Long time no talk. 🙂
We were talking about Internal Server Error message.
Playing with featured images on fresh install WP 3.5.1 and CC 1.12 won’t cause any problem. That error appears when I play with setting featured images after I import a backup database. Sure enough, I always change ‘site URL’ and ‘Home’ in wp_options table to make a backup site functional.
Yet there is some conflict between the backup site CC theme and the rest of the world. 🙂
Not a problem. I will try to run a backup site on another domain just to separate the possible conflict between the production CC theme and the backup CC 1.12 theme.
It looks like a great scientific project, doesn’t it? 🙂
I let you know.
Have a nice day.
thanks for the update!
and let me know the results of your investigations 🙂
By the way, I don’t see that ‘enable image auto fit mode’ feature yet but I just marked this topic as resolved because you figured out that the header was wrongly set.
Thanks for your hard work!
- The topic ‘Header image can't be set, CC 11.1 and WP 3.5.1’ is closed to new replies.