Ed

Perfect! Thank you for the quick response and great support!

Steve,

Yes, that resolved the issue! Thank you!

BTW, you provided a publishpress-pro folder. We are not using the pro version. I was required to disable the PublishPress plugin and enable the PublishPress Pro plugin. How should I manage this going forward? As soon as you let me know, I’ll mark this thread as resolved.

Still waiting for a fix. The last update to v3.0.98 is defective.

khaleeldeli (@khaleeldeli) and Nayeem Hyder (@nriddhi)

Please do not hijack other people’s support thread. khaleeldeli, your issue is entirely different than what I (and some others are experiencing). Our issue has nothing to do with PHP version. The response to your question makes it look like my issue is resolved, which it is not. Have some respect for other people, okay?

This is the problem —>>> edit-store-profile.php does not exist.

@hiroki2020 this worked for me, as well. Thank you!

I’ve updated the version and it is working now. Thank you!

I updated and I can delete results records. Thank you!

WordPress version: 5.2.3
PHP version: 7.2.14

Yes, the fix is working. Thank you!

Vladimir,

Sorry, I didn’t mean to alarm you. I like to keep a couple previous versions of components in case there is a conflict and I want to investigate. Also, my production environment is slightly different than my test environment (I’m not able to get around this). If the pre-test is fine, but there is a problem in production, sometimes it’s easier to roll back a version of a component, than it is to restore from a backup.

I have to let you know that I have updated Shortcode Ultimate in test and prod, but only the test environment is requiring the custom templates to be in the child theme root. In production I didn’t have to change the path of the custom template in the shortcode. Not sure why.

Just saying that I love Shortcodes Ultimate. It is exactly what I needed for our non-profit’s intranet.

• This reply was modified 5 years, 3 months ago by Ed.

Vladimir,

Yes this is working for me now.

Thank you.

Is it a problem if the slashes in the paths are going different directions like this? I notice this in only two of the paths.

stylesheet_dir: C:\wamp64\www\intranet/wp-content/themes/hospice-alliance
template_dir: C:\wamp64\www\intranet/wp-content/themes/spacious

This is the complete error.

Posts: invalid template name

Vladimir,

I had to modify the script or it would error out, but this is the output:

stylesheet_dir: C:\wamp64\www\intranet/wp-content/themes/hospice-alliance
template_dir: C:\wamp64\www\intranet/wp-content/themes/spacious
plugin_path: C:\wamp64\www\intranet\wp-content\plugins
realpath: C:\wamp64\www\intranet\wp-content\plugins

As you can see, I am using WAMP on Windows.

Here is the information Vladimir.

Actual path:
\www\intranet\wp-content\themes\hospice-alliance\custom-default-loop.php

Shortcode:
[su_posts template=”custom-default-loop.php” posts_per_page=”10″
tax_term=”22,21,73,20,23,130,255,256″ order=”desc”]