expresswp

Thanks Benjamin. Good to hear for ACF. I do have the pro version of it, but have several clients that use Toolset WP Types.

I don’t know how WP Types saves it’s custom fields. I do know that they end up with a slug and they have a meta key that looks like wpcf-meta-key and you can even trigger a field using a shortcode. But none seem to work with SEOPress, so maybe they do it differently?

I’ll have to investigate further. Is it possible to allow shortcodes in the titles, or are there limitations that prevent that? Because I know most custom field plugins also allow shortcode triggers.

Regardless, great plugin and I’m considering upgrading, but am just testing out this version for a bit, and love it so far!

Brent

Hey Lyle. Mostly fair points. And don’t get me wrong, I’m not saying everything works perfectly or that there isn’t room for improvement. There is, of course. My main point is that I don’t think it is necessary for them to look up and down BB to know where to go with the plugin. Elementor is SOOOOOO young, and has so much for its age.

BB didn’t let you drag column widths originally, and as far as I could find, you couldn’t even add columns to a row (you could duplicate them and have them appear below, but you couldn’t further split a row into more columns). They added all that functionality later. So it had some growing pains of its own.

Concerning the margins on modules, I don’t get that here. The left and right margins are locked on SECTIONS, but not on modules or columns. Not sure why they are locked, but just wanted to clarify what I am seeing.

I’m not sure I’m having as many problems as you on vertical adjustments and other things. I admit that I probably haven’t used Elementor as much as you, but I’ve done a significant amount of testing and work with it and it seems fairly solid. I do have my own requests that I’ll be posting soon though.

All-in-all, I think Elementor has come a long ways. I did NOT like many things about it when they first released it, and their claim of how great it was didn’t really fit with how I viewed the plugin. But over several updates, it has really flourished. I’ll be very closely watching. I haven’t used it on client sites (I rarely use plugins on client sites until they have a long history of support and stability), but I’ve used it on my own, and I do regular testing. So it’ll be a good few months, I’m sure!

Beaver Builder is also great, but honestly, I have more fun working with Elementor. I look forward to seeing where it goes in the coming months.

Brent

I’m not sure I agree completely. While there are things that BB does very well that Elementor can learn from, Elementor also surpasses BB in many areas. Elementor has more options for many of its modules, Elementor is faster with more instant feedback, etc. I do realize that in some areas such as the API for third party devs, etc. may have a ways to go, but its not like Elementor isn’t better in any way. It actually is, in several areas.

You also have to consider Elementor’s age. BB isn’t very old either, but Elementor is much newer. I think Elementor will get there. Elementor should not aim to be another BB. It has its own way of working and its own priorities. And not to mention that you have to pay for BB (for the record, I do own BB). Elementor does more for free than any other free page builder at the moment. There is some competition like King Composer (another excellent choice, btw), but I think Elementor has held its own.

Honestly, for me, Elementor is comparable to Cornerstone. The difference is that it is BETTER than Cornerstone in almost every area. Considering the team that built Cornerstone has far more devs, I would say Elementor has done pretty well.

Give it time. I like the template library as a feature because people WANT that in a page builder. You may not personally find them a high priority, but some do. Now, there ARE issues for me with getting templates to load. I get errors at times. But I don’t mind the feature itself being there. It’s not like they haven’t been improving anything else, right?

Sorry for the long post. I’m just very excited with where the builder market is. Gone are the days of Visual Composer being the only or best option. There are so many superior options now, we’re pretty spoiled, eh?

Brent

• This reply was modified 8 years, 2 months ago by expresswp.

Great to hear! I’ll update right away. I appreciate the quickness and willingness to fix things. If there is anything I can do, just drop me an email or something. I’m happy to help. Thanks! Have a wonderful weekend!

Brent

Hey! Your new version of the title fix plugin seems to work great! No more errors, and all title options have returned, and titles are being shown properly.

So I think all is well! Thank you so much!

On a side note, I’m working through the finishing touches on my local machine for updating Avada. Your post kind of pushed me to go ahead and finish it for him so we can just get it done. Several little oddities that didn’t transfer exactly, but nothing TOO major.

If there is anything you need, or further testing on any of your plugins, let me know. Thanks again!

Brent

Hello again. Thank you so much for the quick work on trying to fix this! I’m happy to have helped in some way.

I am aware that it is an old version of Avada. As mentioned previously, I’m actually trying to get their site AWAY from it and onto a more streamlined framework. The site had some specific alterations in the child theme that weren’t easy to transition to the newer Avada header system(the child theme code had to be rewritten from scratch to avoid breaking some things), so the update hasn’t happened yet.

I’m working as we speak on testing the Avada update though on a local site, as I believe the trouble parts that were causing the delay have been resolved. I appreciate the little nudge on this though, as I’m actually pretty serious about updates. This was kind of a unique scenario ??

I will gladly try the title fix first before uploading any other changes. I want to help in ANY way I can because I am working on moving all my own sites and slowly getting my client sites away from Yoast. I’ve done extensive performance testing and just can’t justify Yoast. So anything you need, just let me know!

I’ll chime back in after testing once the update comes out. Thanks again for your diligence in this! It is very helpful!

Brent

Ok, sent the debug code. It DOES seem to happen on every page, so I just copied the code from the home page debug.

Please let me know if there is anything else you need. I would love to get this working as I love the SEO Framework plugin. Thanks!

Brent

Ok, just got home. I’ll do all that and copy the debug info for you.

I am working on getting the client away from this theme, as it is one of those ultra-multi-purpose-every-option-in-the-world themes. It is Avada, the biggest selling theme on Themeforest. But as we all know, big selling doesn’t mean properly coded ??

Stay tuned. I’ll send it here in a bit! Thanks!

Brent

Ok, I just checked and the “Remove blogname from title” setting in the “Title Settings” box is completely missing. Not visible at all. I thought maybe it got removed, but when installing the plugin on another site, the checkbox is there.

So I installed the title fix extension, and it completely breaks my site. Deactivate it, and the site works again. With it activated, the site becomes text only with no styles of javascript.

So I’m stuck. If I can’t get this working, I’m going to have to go back to Yoast for a bit. And I do NOT want to do that. Any suggestions?

I’m guessing that all my problems could be solved by the title fix, but since it breaks my site, I can’t use it.

Brent

Redirecting URLs to a PDF or other document is tricky and doesn’t always work right even when done manually, and not exactly what the primary purpose of a 301 redirect is. So I’m guessing this plugin isn’t really designed to do that. It is for redirecting URLs to another URL.

Brent

Just to clarify above, this isn’t just a problem with page builders. It is a core problem with the editor in WordPress itself. All page builders suffer from it because they use the WP builder, which is a modified TinyMCE. But even without a builder, you will get the same annoying problem.

One of the reasons, I believe, is because the “text” editor is NOT designed to be a code editor. It is supposed to be exactly what it says, a text editor. So any “code” it sees that doesn’t seem to have a purpose(such as a div tag without a class or ID assigned) are stripped. It strips out paragraph and break tags as well because it handles them based on line breaks automatically. But they don’t take into account that some people may actually want code in there for specific reasons.

On the front end, the “code” of paragraphs and breaks are still there. They are just handled differently in the backend. And I personally wish they would make this optional so that you really COULD use the text tab as a code editor without having to install a plugin.

It doesn’t seem to be something that is in the works though, unfortunately.

Brent

Hmm, not sure why. I just sent another email. Let me know if you got it. I’ll be on Skype at different times today, so if you don’t catch me, just keep checking. I will try to be on whenever possible.

Thanks!

Brent

I did ?? I’m actually going to be on in a few minutes if you are around. If you don’t see my email anywhere, let me know. It starts with my name, Brent.

Thanks.

Brent

Sure! I will email you here in a bit. I would love to help in any way I can. Thanks!

Brent

For the record, this actually IS a problem with TinyMCE. If you do a lot of switching between visual and text view in the WP editor, you will probably notice it. TinyMCE messes up a lot of HTML code. Also, if you have a <div> element without a class or ID assigned, it will strip the div tags. And it REALLY doesn’t like nested tables.

Anything you can add to prevent this is appreciated. It’s one of those things that has been a problem in WordPress for years because of their use of TinyMCE. Not sure if it is a problem in the core TinyMCE, or just how WordPress itself uses it. But it is a problem.

Brent