Forum Replies Created

Viewing 15 replies - 1 through 15 (of 25 total)
  • Here’s what worked for me (was having the same issue):

    1) Click on Reset All Settings
    2) Click on Clear Cache
    3) Re-enter all fields
    4) Click Save Settings
    5) In my case, check box for Use HTTPS?
    5) Click Re-authenticate with Salesforce

    Nothing worked before this. Wonder if it’s a cache issue.

    • This reply was modified 3 years, 8 months ago by AMC4x4.
    Thread Starter AMC4x4

    (@amc4x4)

    Hi Mike,

    I did look in the classic editor because I saw others had the excerpt option. For me, it’s not there in WordPress 5.5. The only things I have under “Screen Options” are Author, Categories, Tags, Comments, and Date, followed by a Pagination option and View Mode (Compact or Extended – Extended did not reveal an excerpt option).

    EDIT: Looks like it’s theme-related. I found an article that suggested adding this line to my theme’s functions.php, so I did that and it’s good now!

    // Adding excerpt for page
    add_post_type_support( ‘page’, ‘excerpt’ );

    All good. Thank you for the suggestions!

    • This reply was modified 4 years, 3 months ago by AMC4x4.
    Thread Starter AMC4x4

    (@amc4x4)

    I figured out what it was (in case anyone else wants to do the same thing). Took a lot of digging.

    I looked in the database files for my podcast and saw that the older entries had an “excerpt” field populated, while the new post had a blank field. Apparently, PowerPress will pull the <description> content for the post from the excerpt field if it is not empty. If it’s empty, it will pull the entire blog post (or summary, if that is selected in WordPress settings).

    The Classic Editor doesn’t seem to show the excerpt field in each Post composition screen, or perhaps a theme update no longer showed it in the classic editor.

    As soon as I enabled the Gutenberg editor and revealed the excerpt box, I put the same excerpt as I use for <itunes:subtitle> and <itunes:summary> into that excerpt box and now all my feeds are showing the excerpt I want to use in the <description> field for podcasts that use that field for the summary.

    • This reply was modified 4 years, 3 months ago by AMC4x4.
    • This reply was modified 4 years, 3 months ago by AMC4x4.
    Thread Starter AMC4x4

    (@amc4x4)

    Thanks for the answer, Mike. I understand what you are saying, but that is not how the behavior was before. Something has changed. If you notice my earlier episodes, they do *not* have the full blog post in the <description> for Spotify.

    There has to have been a way previously to override <description> being pulled from the blog post itself.

    Is there a place in PowerPress to manually enter what gets put into the RSS for the <description> field for a post when posting a podcast?

    UPDATE: It looks like from this page there is a Google Play Description Field: https://create.blubrry.com/resources/powerpress/powerpress-settings/basic-settings/

    I think once I was able to add that Google Play description, each post used it for <description>. I can’t seem to find that setting though. Can you assist?

    Thanks.

    • This reply was modified 4 years, 3 months ago by AMC4x4.
    • This reply was modified 4 years, 3 months ago by AMC4x4.

    Hello @stevendigital – I was having a similar issue recently on a shared server I pay for that has very limited resources available (the site doesn’t get a lot of visitors, and should technically only require 1/2 cpu and 512MB memory). The attacks were pushing up resource usage way past what was acceptable for my subscription.

    What I ended up doing was locking these out via .htaccess before the attacker could even get to the pages. I didn’t use XML-RPC for anything, so I didn’t need it. I had tried using the XML-RPC deactivate plugin for WordPress, but as we’ve found, that still means hackers can try to get to it.

    I added the following to my .htaccess file and that resolved the issue. I let Wordfence take care of the rest. You could try it and see if you have any adverse effects on your plugins (it didn’t for me). On the wp-login entry, make sure you substitute ANY IP addresses from which you visit the login page for xxx.xxx.xxx.xxx. If you get locked out for some reason, you can just visit the .htaccess file in your cpanel/whatever file manager and comment out everything in that block temporarily until you find your new IP address.

    Hope this helps. It did in my case. Brought the resource usage back down to reasonable limits.

    # BEGIN Block XML-RPC from htaccess
    <FilesMatch "xmlrpc.php">
    Order Deny,Allow
    deny from all
    </FilesMatch>
    # END Block XML-RPC from htaccess
    
    # BEGIN Block wp-login from htaccess
    <FilesMatch "wp-login.php">
    Order Deny,Allow
    deny from all
    allow from xxx.xxx.xxx.xxx 
    allow from xxx.xxx.xxx.xxx 
    </FilesMatch>
    # END Block wp-login from htaccess
    • This reply was modified 5 years, 2 months ago by AMC4x4.

    Thanks, Scott, for maintaining this as long as you did with all the challenges. Cheers.

    I opened a Siteground account a month ago or so (so it’s one of their “new” accounts without cPanel) and so far no issues with Wordfence. Didn’t need anything special to set it up either as far as I know. Can you clarify what the “few extra steps” would be?

    I have an old Siteground account as well which is still on cPanel, but I’m closing that one as of tomorrow. I don’t remember doing anything extra to set up on that one either.

    Thread Starter AMC4x4

    (@amc4x4)

    Thanks Dave! I guess my confusion was that I expected to see that IP “blocked” automatically once it tries to access a banned URL to not even give them another chance to try again – notice in your screenshot the “Block IP” option is still available.

    I’ve just started using this amazing plugin and it’s been incredibly helpful, so it’s probably just a matter of continuing to educate myself about how it works. I hope to have enough cash to purchase a sub at some point!

    Thanks again…

    Discussion says proxy hack isn’t working anymore. I guess this plugin is doomed?

    Had the same issue as everyone else until I rolled back to an old version. Wonder why developer doesn’t seem to be addressing this??

    Same here. Guess this won’t be fixed.

    Same issue here. Everything was fine until I switched my site to SSL. The only way the files will load now (without a 403) is if I tick the box that reveals the whole URL, and then the file opens in an insecure window. I can’t believe there are so many questions about this with no response from devs.

    Oh, and Joachim B, thanks for the suggestion, but in my case, Postman didn’t help.

    Yep. Posted weeks ago that I am stuck on version 4.5 of contact form. Any upgrades past that break my forms and the messages appear to be sent, but there is no confirmation message and no rejection message. It just looks like its sent, but isn’t. The form contents are registered in the database though, it’s just that the message isn’t sent.

    No response to any of my inquiries here. Wish they had paid support, because I’d actually pay for it.

    Forum: Plugins
    In reply to: [Contact Form 7] Broken
    Thread Starter AMC4x4

    (@amc4x4)

    No ideas?

Viewing 15 replies - 1 through 15 (of 25 total)