worldmaker
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [Responsive] Update to 6.1.0The way I understand the shift in the design the new Header / Footer Builder give you three layers. Thus: Above, Header, Below.
If you are getting the Builder to activate when you select Header in Customiser you will see these three layers at the bottom of your page, with items like “Widget” featured and the Settings cog wheel icon on the left.
Hit the Settings and you should have some control over each of the three layers in the header. Part of this is the ability to have 1,2,3,4, column layout on the layer, then you can drag and drop the widget or whatever into that column box in the Builder at the bottom of the page.
Layout or each row, item, column, left, centre, right justification, is the real challenge I’m having and just wrote to Support for any clues as to use a CSS override but I don’t know how it will work with multiple columns.
So for now we’re all in the dark while the Chimps burn the midnight oil.
- This reply was modified 1 year, 3 months ago by worldmaker.
Forum: Themes and Templates
In reply to: [Responsive] Update to 6.1.0Here are my latest up-dates, I will copy these to Support in a few minutes but leave them here for anyone else with issues.
I’m beginning to understand how 6.1.0 has differed from 6.0.3, but still getting used to it.
One change was the background colour of the header menu – this has moved from the menu settings so the upgrade demands you go find the new location of the header menu’s background colour: Customiser\Header\Below Header\Design (change the colours).
This leads to another issue: the layout of the header is gradually moving to the new Header / Footer builders, which ought to pop up automatically with the grey-shaded panels across the bottom of the page when using the Customiser (click Header / Footer and they pop up, sometimes). Here you can fool around with the layout and control formatting. However they break sometimes and need a refresh, or something to trigger them. It seems to be an intermittent fault on my system, no idea why. I can live with it.
With the new header I have an issue with the layout of the header, logo, site title and the header menu. I have three Responsive sites each with a different layout for the header: 1 (norfilms.com) is centred title and menu (no problem – do not touch), 2 (bookofhappiness.co.uk) is left-justified and I had to make a CSS override to achieve that, 3 (worldmaker.org) is the challenge with a centred title and left-justified menu, and I haven’t found an easy way to code that one yet. In other words the default is centred and there appear no controls for any other styling. I think this will be a big issue for many developers or businesses designing and styling their own sites.
That’s it for today.
Forum: Themes and Templates
In reply to: [Responsive] Update to 6.1.0I’ve been in touch with Support over the last couple of weeks to explore the various issues I’d been having.
There were a number of challenge I’ll document here for anyone else having a similar problem.
My header was showing white across the page, although it’s been customised to be transparent.
The footer showed one widget and the copyright text centered when they were originally aligned to the left.
There was a minor issue with the “li” ordered/unordered list settings.During my exchanges with Support they took me through the changes to the footing in the customiser – new panels/controls at the bottom of the page – grey-shaded element that now control the layout and display of the footer. Support were good enough to show me a little video on how to correct my footer using the new controls down there. This resolved the layout of the widget and copyright.
The issue with the “li” code, were I use a CSS override to format lists, but which was causing an issue with the use of “li” in the header menu, was solved with a little code snippet for my to add to my CSS override to protect the header menu from my other formatting.
The white header took an interesting turn when Support said they couldn’t see it. It made me realize that perhaps they were viewing my web site in a modern browser. I checked with the latest windows 11 in Firefox and Chrome and there was no issue. This made me realize that the issue I’d been seeing was only occurring in older browsers under Windows 7 and XP (I design and test here to ensure backward compatibility). I suspect Responsive 6.1.0 has a little issue with older browsers. Support sent me a snippet of code to put into my CSS overrides and fix the issue.
Conclusion
I suspect some developers and perhaps many site visitors are having problems because of the new formatting feature in the footer area when using Customiser and some incompatibility with older browsers. And I suspect Support are busy fixing this as I write all this.
I will be adding all the snippets and updating my sites in the next couple of days and happy to use 6.1.0 from thereon.
Great assistance from Support team throughout this experience.
I’ve just sent my latest thoughts over to Support but I will post it here for anyone who has a similar problem.
My “broken” site included a “whiteout” for the header and this was causing problems until I realized Support couldn’t see it. It made me think that they are using the latest browsers while I design around older ones to be compatible with the largest possible audiences. When I review my “broken” site under Win11 and a modern browser, Firefox or Chrome, no problem and no “whiteout”. This has made me believe that it is a compatibility issue with older browsers and anyone developing or viewing a site with older machines (millions and millions of little chimps around the world).
I don’t know if Support can solve it as they are trying to improve performance with new design features which may not be backward-compatible, but I’ve laid down the challenge. I await results with interest.
Oh, and they have successfully helped me fix the broken footer, so only one challenge remains.
- This reply was modified 1 year, 3 months ago by worldmaker.
Forum: Themes and Templates
In reply to: [Responsive] Update to 6.1.0I think they’re busy with the 6.1.0 issue.
I just sent them my discovery so I hope they can solve it or many of us will have to stay with 6.0.3.
Forum: Themes and Templates
In reply to: [Responsive] Update to 6.1.0I too am having a few problems with 6.1.0, but close to solving it all (I’m taking a break from writing my report to the Chimps).
Here’s how to fix your challenge.
Go to the plugins pages and get, and activate, a rollback plugin, eg, WP Rollback. This allows you to roll back to earlier version of themes or plugins.
Then update to Responsive 6.1.0.
The go to your Themes page and select the theme’s “Theme Details” button when you hover over it.
This opens the description and you will see some buttons along the bottom, one of them being “Rollback” (it’s at the right-hand end for mine).
Select to Rollback and wait for it to perform its magic to show you a list of previous options.
Select 6.0.3. (I don’t think that one is “broken”).
Wait while it fetches and installs the older theme for you.
Enjoy you time until we all fix v.6.1.0
Up-date.
Recent up-dates to the plugin seem to have fixed it and it is now sending from my forms.
Switching reCAPTCHA back on to stop the spam flood I’ve been receiving.
SOLVED (Partly):
Yesterday, while testing a new contact form, after the first three successful test mailings into my mail boxes, it stopped with an error message :
“There was an error trying to send your message. Please try again later.”
I spent the last 24 hours trying to work it out, was it a server issue, a faulty plugin, or me just mistyping an entry on the form while creating it?
THANK YOU @glenneaton for the tip about reCaptcha
I DID see a red alert message in the corner of my browser, tucked half out of sight, but thought it was another issue (I have just changed domains to a shorter version of my site and thought reCaptcha was referring back to the earlier version).
I’ve followed your advice @glenneaton and the problem vanished. All forms are now clean.
Now, I think it’s upto the developer to figure out what is happening and how to work around it, a form without reCaptcha is going to be vulnerable to bots, making this only a part-solution to the problem.
I will await an update, or news.
NOTE to the developers: I have several sites, only one appeared to be fully faulty. Another site showed the error yesterday evening, then cleared this morning. Now I have to wonder if it is a case of reCaptcha and Contact From 7, plus some other feature, another plugin or theme, and will the other sites catch this bug at a later hour? Mysterious.
Forum: Networking WordPress
In reply to: New Network, Domain Mapping OK but Dashboard not availableThank you for your prompt advice.
I’ve tried a clean .htaccess file, with nothing but wordpress code, and no change there.
As far as I can tell all the SSLs are routing correctly, all on the same server for both the parent location and the mapped domains and all part of one SSL package for all my sites.
As you know the mapping works for visiting the site but not for the Dashboard, so that makes me believe it is internal to WordPress itself. Perhaps because I have the site rooted out of a folder under the parent domain this is not working.
As for my service provider. They appear to be WordPress-friendly and there doesn’t appear to be any problem with me managing several sites off the one service package.
I wish I could do more but I’ve no time or skill. Perhaps I will try to raise this as a technical challenge for the developers to look at.
Forum: Networking WordPress
In reply to: How can I add a domain in multisite?I’ve successfully used a plugin called Prime Mover to take a single site into a subsite.
Forum: Themes and Templates
In reply to: [Responsive] upgrade from 1.9 to 4.7From an outsider’s point of view my best advice is create a test site separately and carefully migrate the content and structure, design the work around needed, test it thoroughly, then conduct an overnight up-date of the old site, transfer all settings from test to working site and you should have the results you need.
There are plugins you can use to export all customiser settings from test to working site for swift change-over, and export the old site in case you need to roll back to fix any issues.
Hope this helps.
Indeed, it appears to have been revolved as there are no further issues and no alarms on installing updates.
Sorry for the delay in getting back. Busy times.
Forum: Themes and Templates
In reply to: [Responsive] White Text on White BG in the EditorThanks for that.
That looks like a long way around the problem, as I’ve never had to do anything like this on other sites, but it has done the trick and I can now read my pages in the editor with white text.🙂
The “Fatal error” I copied from the update is all I have to offer. I never reproduced the error as it was caught by the WordPress system during the last update to the plugin.
I have had no further errors and there do not appear to be any issues with the web site at this time.
Forum: Themes and Templates
In reply to: [Responsive] White Text on White BG in the EditorTejas
Here are a few of the steps I took originally.
First I decided to mark the text as white using the editor. Note that I am using paragraph boxes inside a Row Layout from a Kadance plugin block, to give me a narrower column of text. Although I have also tested without such a feature and had the same problem.After setting text white I saw that it was invisible against the white background of the editor. I then removed that text colour setting and used the customiser to create a global typography setting for paragraph text throughout the site.
When I returned to the editor the text has remained white, even though all paragraph colour settings have been removed (see exception below).
In this instance I was creating a page, but the same effect seems to appear when creating a post – the entire editor is white throughout.Here’s the page I was editing…
http://www.sterlingsecure.co.uk/bondevzoneWP/beeland/
Here is a screenshot of the editor page.
I have highlighted some of the text to illustrate the issue, and the B.E.E. heading (not a Header, as that is also invisible in white) has been set to black for visibility here, although it returns to white on the web page.http://www.sterlingsecure.co.uk/bondevzoneWP/wp-content/uploads/Responsive-in-White.jpg
I wonder if there is some setting that is not being flushed from the database when I was making these shifts in the settings?
As I mentioned originally, I did a test on another site with the WP default Twenty Seventeen theme, white text in the customiser and no playing around with text colour in the editor, and had no problem with retaining colour in the editor.Hope that helps.