Forum Replies Created
-
Posts
-
Many thanks for your answer.
No, there is no translation available for that theme.
But you are right: I will contact StudioPress support. It had not come to my mind to do it, since the only time I had contacted them, they had advised me to go to the forum for help. But it was a different type of question, while that one certainly it is a support relevant question.
Thank you, Christoph. Once the website goes live, I will share the URL and show the issue, if I have not been able to solve it by then. (Or explain how I have solved it, in case I do!)
If I have several more issues, I may also contact you privately for customizations. But first, I want to complete the process of moving my content to the new WP environment, and see which issues will possibly remain unsolved at the end. This is also part of the learning process: attempting to find solutions by oneself insofar it is possible - then it makes it easier to manage one's website on a daily basis!
(I had answered Andrea's post, but strangely, it seems nowhere to be found, thus I repeat it.)
I use the most recent version of WP - always keeping it up to date, this cannot be the issue.
Since I had not realized that the plugin might be the cause of the problem, I had not checked comments about it (it is a legacy site I am taking care of, I had not created the original website myself). But considering there are other reports about issues with that plugin, I would rather stay away from it if it has not been updated for 8 months. Maybe you can find another plugin? Good luck!
(In some cases, frequently updated plugins can also cause trouble: I had problems with contact forms after the recent updates of Conact Form 7, and I gave it up and switched to other solutions. Fortunately, for contact forms, there are other options that can easily be implemented.)
Yes, you are right, I assumed also that it was supposed to work with it, but it didn't.
I am always using the most current version of WP - I keep it up to date. Thus it cannot have been issue related to my WP version.
The fact that a plugin has not been updated for 8 months is not always an issue, as you know, but in some cases it can indeed break functionalities. Considering the other reports of issues with it, I would rather be cautious before using it. Maybe you can find another plugin with similar functions?
(Sometimes, updates of plugins can also create trouble: I recently gave up using Contact Form 7 after their recent updates, and switched to another solution - too much trouble with fixing issues. Fortunately, for a contact form there are other options that can easily be implemented.)
I have found the root of the issue, after losing hours attempting to solve it! On the front page, there was a "Feature tabs" widget with three stories (one could click on categories such as Domestic, International, etc., in order to be able to see the featured story of interest (there was even the option for more. You can see a screenshot here:
http://tribulatio.com/featured_tabs.png
When I removed that "Feature tabs" from the front page, the problem was instantly solved.It had not come to my mind that a widget could compromise in such a way the viewing function of the Customize area! I hope that my little experience can help other people who experience similar issues.
Interestingly, while live preview with Genesis theme works fine, the same issue occurs with all child themes.
Wondering if the previous editor of the website made some customization that causes the behavior. But quite difficult to guess what it can be, since I cannot "deconstruct" the theme... And if the issue has to do with customization, why does then Genesis theme itself work fine, while the issue occurs with child themes? Puzzling...
I will probably apply the new design to my website next week, and I would really appreciate to know if my way of doing it as I have planned it above is correct? Just in order to avoid making some major mistake without being aware of it.
Thank you!
P.S.: for exporting a theme, I see that there exists also another plugin:
Just to add the answer, since I had included it in another post - I had finally found the trick to do it:
Instead of creating exceptions, to keep the width to 100%, but at the same time to set a maximal width. For instance:
width: 100%;
max-width: 675px;Then, for any screen less wide than 675px, a responsive theme will automatically use the full-width, thus avoiding various issues encountered with my previous attempts.
I have still to find the syntax for such a rule in smaller media queries - but it is quite late right now here, so I will stop for tonight and see tomorrow how this should be done.
Thank you once again!
Thank you for your remarks.
Yes, definitely an issue with smaller screens. When I had reduced it to 80%, it was working fine but it left empty space on both sides on the smartphone screeen too, hence my idea rather to choose 675px. Maybe not the best idea after all...
No ads at all on the website.
It solves my problem except for smartphones: I have made tests on my iPhone with sevewral browsers, and with all of them half of the screen is occupied by the background image (which didn't happen without "float"). I don't know if you have any explanation for that? (I should say that the server on which I am doing the testing is not a powerful one, but still I don't think that it can have an impact on the way pages render.)
I have made a screeen capture on my iPhone in order to show the issue:
http://tribulatio.com/images/smartphone_screen_capture.pngThank you! You are right, this is excellent! And moreover, your answer has taught me how to use some CSS functions I wasn't familiar with.
Probably I should also try, rather than to set content to 80 %, to choose a specific width: in that way, it will probably even show better on a smartphone. I will try that right now.
Many thanks for your helpfulness!
Yes, you are right.
It is a mock site - based on an export of my real site, but not with its real title and some other changes, since I am in atesting phase before implementing what I have in mind on the real site. I have come back in the meantime to 1,200 px for testing purposes, but anyway this is not relevant to my issue.
Here is a link to a full-width page brought down to 80% by using:
.full-width-content .content {
width: 80%;
}http://tribulatio.com/test/2015/11/suisse-radio-television-religion-rtsreligion/
I do anyway realize that it is NOT a good idea: not only it brings the content area either to the right or to the left, but not to the center; but moreover, it renders awfully on a smartphone screen. Thus this is NOT the trick I am looking for, but I leave it as it is for the time being. (And it is still too wide, but if I would reduce the theme to 1,000 px plus some padding on both sides, it would probably be right. However, it would still remain to be seen how it would show on a smartphone or other small screen.)
Of course, at the end, I might decide to keep the sidebar on full article pages: this would solve the issue. Let's see if some better ideas come from this discussion.
Many thanks for the explanation. Extremely useful: I had been misled by the word "Archives", and had not realized that the settings here would apply to any list of articles. Thus I substituted "260" with "0", and it was done. I had not understood that I should intervene there. Your answer has solved my problem!
