davidmcc3

Hi Bryle

Thanks for the reply. This is the link to today’s log:
https://pastebin.com/h0WiVNcu

Unlisted, expires one week.

Regards, David

Hi

I’ve encountered the same problem, and the CSS fixes it, but shouldn’t this have been added to the plugin so the problem doesn’t occur?

According to the info on the WP Plugin page, the plugin has been updated since this thread was started.

Thanks, David

• This reply was modified 5 years, 2 months ago by davidmcc3. Reason: tick email

Hi Aert
Ticket raised about 12 noon UK time Monday 19th
Using my full name David McCarthy
Address on form was my ideas-right domain

Hi Aert
Ticket raised with details for access to site.
Regards, David

Hi Aert
I have my dev version of the site. It is using WP4.6.14 and PHP 7.0.33
I’ve deactivated all plugins, and activated the 2012 Theme.
I installed Complianz-GDPR (3.0.9)
Running through the wizard, got past adding company name etc. then site crashes and displays HTML 500 error message in browser.
If I rename the complianz-GDPR folder on the server, the site is instantly restored.
Having had this problem once, I can delete the plugin and reload it, but as soon as I activate it, site crashes again with 500 error.
At this stage, I can’t see the website or the WP admin area until I delete or rename the plugin folder.
I’m completely baffled.
Regards, David

Hi Aert

Thanks for your quick response.

I’ve created a dev copy of the site, so I can disable plugins to find the conflict. This much I can do myself, and I can report back my findings.

Can you confirm that WordPress version 4.6.14 should be okay?

The hosting account is running PHP 7.0.33

Regards, David

Scott’s right – IE’s 4% is an important number.

This situation is worse in the UK. Current stats for the last 12 months show:
IE – 5.27%
Firefox – 5.23%
Edge – 4.87%

So Microsft have 10% of the UK browser market (accross all devices from desktop to phones).

It doesn’t matter how wonderful Elementor is (and it IS wonderful), if a particular sector has lots of IE/Edge users, having a broken site is a deal-breaker, and spells the end of Elementor for the project.

I don’t believe this has been changed yet?

Doubly important now WP5 has landed!

I’ve just had a report from a user that they can’t view the site in IE11 … it is broken and fragmented.
I’ve seen on another thread a link to the Elementor requirements, and it clearly states IE can’t be used for editing.
However, it also says:
“In any case, pages built with Elementor will show up in all the browsers.”
This is obviously an incorrect statement.
I don’t have IE 11 on my computer … the most recent IE I have is the IE 9 that came with Win7. That also doesn’t display the site … in fact it says it can’t connect!
Can we either have a fix so IE 11 can view the pages, or have the Elementor Documentation changed to reflect reality.

PS. Here in the UK, IE is still showing in Statcounter Global Stats as having 5% of browser use (October 2018)

• This reply was modified 6 years ago by davidmcc3.

Hi David

I concur with much of what you say – the current IT industry is chock-full of companies changing the way things work and creating waves of pain, confusion, and expensive re-training. The problem is always that the change doesn’t deliver any benefits – my Word documents can as easily (more easily) be written with Word 97 as Word 2016.

The problem with far too many recent websites is that they are design-led. Designers have forgotten their audience, and are just showing how cleaver they are. They should have left that behind in art school. Most too, have no conception of typography and its part in design and getting the message across.

I don’t do code either (30+ years in IT supporting hardware and then users, up to Director level), though our first two sites were html (with Dreamweaver). I’ve had to learn the rudiments of CSS so I can style where the theme or plugin doesn’t provide the tools. Which brings me to the underlining of links – I’ve discovered the UK’s Guardian Newspaper has this off to a tee … I’ve creatively swiped their CSS and use that on all our sites. It’s very smart, and doesn’t actually use underlining … I alter the colours a little to suit each site.

If Guteberg is in WP5 core, all the sites I build and manage will stay with 4.9.x – I won’t use WP5 and then add to code size and slowness by using a plugin to get back to Classic.

If it does prove to be the failure we both fear … there will probably be a fork, and WP5 could very well wilt on the vine.

I so agree with your marketing perspective – a website is a marketing tool, not an end in itself.

Best regards, David McCarthy

Hi Marius

I suspect your statement:
“You’ll see page builders are already experimenting with and planning for how they’ll work with Gutenberg, as most of them see this as a great foundation to build on.”

… is both optimistic and blinkered … I would guess the page builders are experimenting because they know they they will have to live with Gutenberg, warts and all, if they want to continue in business.

Hi Cory
Thanks for the quick and full reply.
I’ve been using Duplicator with almost zero issues since 0.2.7, so it was a big surprise to have these problems.
We moved hosting in August as our previous supplier was taken over by a much larger hosting group (Paragon), and the quality and level of support dropped dramatically. The new company, Certa, have been providing excellent support … so it’s disappointing to have these problems. The previous duplicate taken from this site before the last update, was a few weeks before we moved hosting!
I checked the feedback for Duplicator (I always make checks when there’s an issue with a plugin), and couldn’t find any sign of a major problem … as you have confirmed.
They are cheaper than the previous supply, but we’re not cost-driven … it’s service which is important. I’d hate to move again … but we’ll see how they respond when I get back to them.

Sorry … forgot to mention excellent blog on https and security by Troy Hunt … I won’t try to post the link, but search on “Life Is About to Get a Whole Lot Harder for Websites Without HTTPS”

Hi Yui

I’m not suggesting WordPresss.org makes HTTPS compulsory, but the facility should be in the Core, not as a plugin – we all know plugin support comes and goes.

As of October, Chrome (the market leader) will be marking ALL pages with the ‘insecure connection’ if there is an entry field … this includes any ‘Search’ box, the from/to boxes for route planners etc. Other browsers follow where Chrome leads.

The WordPress.og and WordPress.Com sites are https … so why is it missing from the Core? I’ve looked at Dev chats recently, and I haven’t even seem it mentioned!

From the point of view of visitors to a website, https transport layer security is far more important that Gutenberg. And who do we build websites for?

Check the HTTPS topic tag, and there are lots of people struggling to get https working properly … about time the Core development teams woke up to the problem.

PS. My IT background (30+ years corporate and SME) has been on the customer support and account management side. While I understand lots about the technology, I’m not a programmer or coder (never mastered the skills) … I’m a user advocate … so that is my perspective.

Hi
Thanks for the response … email sent.
I can confirm the errors stopped as soon as I deactivated the plugin.
Look forward to hearing from you.
David