cedialogs

It has been a while since I used the plugin, but had to stop using it because it was generating broken links that were difficult and tedious to run down and fix, even with a link checker. Upon reflecting on the problem I recognized that for the plugin to find all the links that it might break would be a daunting and time-consuming task for the plugin. This would really get tedious for the plugin to police on a large site with many links.

Whoever designed WP had no clue about the difference between absolute and relative links or why it matters. As a result, staging or moving a site is a daunting nightmare. And no, blitzing the absolute links with a global string replace is a bad answer.

BTW, I am not a cat person, but I have known a few rare cats that really were good cats.

In the free version of Elementor templates must be updated manually on a post by post basis. The paid version of Elementor will do what you want.

The ideal solution for this situation would be to use Server Side Includes (SSI) if your server is an Apache server. In my case, WordPress and/or my hosting service blocks SSI’s as a security risk. I fail to see a security threat here if you know what you are doing.

• This reply was modified 3 years, 10 months ago by cedialogs.
• This reply was modified 3 years, 10 months ago by cedialogs.

It should work, provided your page builders allow access to HTML in the situations where it might be necessary.

Try editing your text in HTML (text) view and put <p></p> tags around the paragraphs. This works great for me.

I have found that page builders such as Elementor and Gutenberg are flawed enough in their implementation that occasional resorting to HTML is necessary even though the developers of these packages falsely insist that no knowledge of HTML is needed to make a page look great.

When will you be able to say that this plugin is tested with the current version of WordPress?

I am sure that code refactoring has been a step in the right direction, but neatly re-arranging the bugs in this entomologist’s paradise does not fix anything.

Amen.

• This reply was modified 4 years, 5 months ago by cedialogs.

I tested your page using the latest releases of Chrome and FireFox. It appears to work as intended. The biggest problem by far that you have is your choice of a very light gray player on a white background. This makes the player almost invisible.

I feel your frustration. Even though you are developing in an Apple environment, whereas I am developing in a Windows/Linux environment, I suspect that this plugin screws everybody equally, all in the name of fairness. The main problem appears to be atrocious workmanship in the plugin itself and/or its lousy documentation. I think I have AWS working, but can’t prove it.

I am about ready to declare the man week I invested in getting nowhere to be a complete loss.

My sympathies. Stay safe.

Thanks for your response. It looks to me that most or all of the problems with the AWS plugin are on the plugin side, not the AWS side. With some charity, the AWS setup was a success (as far as I know) despite its having security that was designed for the CIA. This plugin’s problems are a tragedy since there are many WP plugins that are stunningly good pieces of engineering.

After going through hundreds of plugins, AWS is the only one that does not work even a little bit under any known conditions. If it weren’t for many other excellent plugins, WP would be engineering rubbish.

Being an author of sorts, I wanted to spend my time on generating content and not on constantly having to reverse-engineer the ill-thought-out basic design of WP itself and debugging flawed code. I have spent almost as much time outsmarting design and coding bugs as I have on building content.

For instance, the WP design’s fragmented modularization precludes having an orderly, centralized control panel, and using absolute links where relative links would do creates much grief in staging and relocating sites. Automattic Airline seems to have implemented many great ideas in building and flying its Boeing 737 Max 8. BTW, why is automattic spelled the way it is?

After 7 spending years, part-time, learning how to outsmart WP’s design flaws I am finally (except for AWS) spending most of my time on content and presentation issues.

Thanks again for your response. Here is hoping that the AWS plugin can be made to work and that our efforts will not have been wasted.

Stay safe, and hope that the likely second wave will not happen.

This is an addendum to my “jetpack mobile theme shortcodes” post. It appears that shortcode value substitution may be exacerbated by a very fundamental design flaw in WordPress. It appears that the processing of shortcode substitutions is not recursive.

This means that any embedded shortcodes appearing between a shortcode opening tag and a shortcode closing tag are not processed. As long as shortcode opening tags and shortcode closing tags are allowed in the system it appears that the text between them must be processed recursively to perform the requested value substitution. Am I right? If I am right, the failure to recursively process the text between shortcode opening and closing tags is a serious design flaw in WordPress.

This link does not work for me either. It offers to download a file called “mpeg”, but no such file exists. No file of any kind is downloaded. The requested mp3 file is located in the media library. The podcast media player finds and plays this file.

• This reply was modified 7 years, 11 months ago by cedialogs.

Are you using the latest versions of your operating system and chrome? I use Chrome, not Chromium, on Windows 10, Android, and Linux. Chrome handles this plugin just fine in all case.

Thanks, Michael. I was given an alternative approach that is rather klunky but does seem to work.