zdmdesigns

This bug is still present as of today, which is unacceptable, especially for an Elementor Pro customer like myself. It doesn’t take 5 months to fix a bug as obvious as this.

Since Elementor doesn’t seem to care, I found the fix myself, which is to make Elementor > Settings > Features > “Optimized Control Loading” > Inactive.

• This reply was modified 6 months, 3 weeks ago by zdmdesigns.

Sounds great. I look forward to it!

If anyone is interested I found them in wp_postmeta > meta_key =

• _oh_add_script_header
• _oh_add_script_footer
• _oh_add_script_header_hide
• _oh_add_script_footer_hide

This doesn’t seem to have fixed it, but thank you for your suggestion.

The problem is still prevalent.

Hi Sami,

My apologies for not posting a response. Got so busy, I forgot. Your solution worked great! Thanks for helping me out on this.

Please also make sure the filter removal restores the default single in-post edit permalink behavior for ALL USERS. I noticed when commenting out the filter code in class-custom-permalinks-form.php > line 19, it only restored it for those posted by my User.

Got it to work, but I had to create a shortcode attribute first that matched the child page slug and insert that as the get_options_page_id. Not really a seamless solution.
Pain in the butt…

• This reply was modified 6 years, 4 months ago by zdmdesigns.

Follow-up… Save yourself the grief, and download AH Display widgets, which actually allows you to use the preexisting logic you had in the now defunct and deprecated Display Widgets plugin.

https://www.ads-software.com/plugins/ah-display-widgets/

Here’s my review: https://www.ads-software.com/support/topic/does-not-work-poor-support/

Agreed:
https://www.ads-software.com/support/topic/does-not-work-poor-support/

I see that no answers are ever given here. Posts go months without a response. I was considering buying the premium version of your plugin, but if this is how customers are treated before they buy, I can’t imagine how they’re treated once you have their money…

I’ve already reinstalled so many times my fingers are bleeding. Please see below instead of a screenshot.

1. This is exactly what was entered (see line item a below). I removed line item b, but left line item c intact.

2. The default entries were:

line item a:
• left entry = localhost/site
• right entry = domain.com/folder/site (I changed this to site.domain.com)

line item b:
• left entry = /site
• right entry = /folder/site

line item c:
• left entry = (blank)
• right entry = wp__

Hopefully this helps.

Getting closer…

I entered utf8 and utf8_general_ci as suggested and the site installed, and I can even get to the /wp-admin page. But none of the images are showing up. So I ran the trusty interconnect/it DB S&R and there were all the db references not changed… about 1100 of them (I selected all tables in the last S&R Akeeba step, not just the WordPress core).

I’m uploading from my localhost XAMPP to a sub-directory on my live server (with an sub-domain pointing to it). When I use interconnect, all I have to do is localhost/site =(changed to)= site.domain.com and it works flawlessly.

1. Why did Akeeba miss all those references?
2. What is the “wp_” there for in the last S&R step, and is it needed (I left it there not wanting to screw things up; didn’t the db tables already get prepended with wp_ in the earlier step)?

Will do Niko. FYI, I never added that php closing tag, as I don’t create wp-config files from scratch, I just edit the three effected values for installations (DB_NAME, DB_USER, DB_PASSWORD (DB_CHARSET (if needed))). That closing tag was there when I inherited this website. That is good info to know though.

On another note, does Akeeba regularly change php file code when compiling or restoring? The reason I ask is that I had an older Joomla website I used Akeeba for and found that the backups became unusable because extra lines of “empty code” had been added to many files throughout the site. Ultimately the website was old and a new one was needed, but it would be nice to have that website available for my portfolio, and at this point, I cannot install it without errors.

“It’s an architecturally incorrect solution, but if the architecturally correct solution earns us two-star reviews…” Quite a blunt statement lol. I understand your desire to keep your reviews clean and accurate. If the solutions you’ve suggested work, rest assured your review will be revised.

I’ll do as you’ve suggested and get back to you.

First issue: After many failed attempts to restore, I found that Akeeba Backup added an empty line to the bottom of my wp-config.php file causing a “header has already been called” error when trying to restore via Kickstart 4.0.0, making it impossible to get to my /wp-admin page and set the permalinks after the database restore. This was a major source of frustration.

When I finally did get it to where I thought the database restore worked, the results were corrupt. Copyright symbols and em dashes turned into diamonds… entire sections of the website did not appear (sidebar).

For Joomla Kickstart I always use the intuitive defaults (check boxes) and it works brilliantly. For WordPress I was hoping for the same. Maybe I need to un-check or check a box?

I appreciate your offer to help because as I stated before, I’m a die-hard Akeeba fan and would love to do away with my Duplicator and switch to Akeeba for WordPress, but I was really let down. I love your extension so much that I was trying to figure out how to still keep using Akeeba Worpdress, just without the database section (which is what I ended up doing to get it to work). Ultimately though, this won’t work for me in the long run and will prove to be more of a hassle than anything.

Happy to revise my review if you can come up with a solution. A glowing review is not out of the question.