jenvander
Forum Replies Created
-
Forum: Plugins
In reply to: [Popups for Divi] Popups for Divi removes other click handlersHello, I am also having this issue. I need to bind an on(“click”) function to the button that launches the popup, but Popups for Divi is turning off all other registered event handlers, and thus cancels my bind. Can you either remove that offending .off() code or provide us with a way to add our actions to the execution list?
Forum: Developing with WordPress
In reply to: Started getting warnings in class-wp-query.phpWell, I found the hooks being called the hard way, and it does seem there was a WordPress update within the past few months that caused this warning to appear. Anyway, I found a workaround.
Forum: Developing with WordPress
In reply to: Started getting warnings in class-wp-query.phpWell, I understand your response, however, I’m not convinced that the problem really is my plugin. I think the problem is in WordPress, because everything was fine before the recent upgrade to 6.1.1. Now I’m getting errors in a WordPress PHP file, but I don’t think the problem is with my plugin. I think I’m doing things correctly, but there is a problem in the recent WordPress update that my plugin has tickled. All I’m asking for is a just a few hints, such as which hooks might be running on that wp-admin Pages page, because *nothing* in my plugin should be running in that page at all, so I think that’s yet another hint that something’s going wrong in the recent WordPress update. If you can give me a link to a page that tells me everything that WordPress does when it loads the wp-admin Pages page, that could help a lot.
Forum: Developing with WordPress
In reply to: Started getting warnings in class-wp-query.phpPlease re-read my post. I know exactly which plugin is causing the issue; it’s mine. I wrote it. My plugin was working without issues with previous versions of WordPress. These warnings appeared with version 6.1.1. I posted this in “Developing with WordPress” because I’m developing with WordPress, and that seemed like the right match.
Forum: Plugins
In reply to: [Easy Watermark] Not showing custom post typesWell, I peeked at the GitHub code and saw the line:
if ( post_type_supports( $post_type, ‘editor’ ) || post_type_supports( $post_type, ‘thumbnail’ ) )
So I added ‘thumbnail’ to the ‘supports’ array and voila! It worked! This might be a good addition to the FAQ for people developing plugins that want to support Easy Watermark.
Update: I set this to the v2 “I’m not a robot” setting so that we could have the form working in the meantime. Let me know if you need me to set it back to v2 invisible for testing.
Forum: Fixing WordPress
In reply to: Can’t log into wp-admin, something keeps rewriting URLs to httpsI figured it out, and it’s an oddball thing. So another site hosted from this hosting account was updated to use SSL. The Thistle site lived in a subdirectory underneath that other site. The hosting company’s Apache server must only be reading the top level .htaccess file, instead of the usual hierarchical order, so that other site’s rewrite rules were being used instead of the actual Thistle site’s rules. So, all I had to do was move the files for the Thistle site up one level so that it was no longer nested under that other site and voila, it worked. Yikes.
Forum: Fixing WordPress
In reply to: Can’t log into wp-admin, something keeps rewriting URLs to httpsI had renamed the plugins directory and it made no difference. Is there another action that I need to take to “turn off” plugins?
Forum: Fixing WordPress
In reply to: Can’t log into wp-admin, something keeps rewriting URLs to httpsWell, indeed it is hosted where originally indicated. The WhoIs was a red herring. I re-installed a new WordPress site and it showed up, working. So I’m back to, what in the heck is doing those rewrites when I use the original files and database? If .htaccess has no effect, what else could do the rewrites?
Forum: Fixing WordPress
In reply to: Can’t log into wp-admin, something keeps rewriting URLs to httpsWell heck, I’m wondering now if this is even hosted where I was told it was hosted. Whois has something different to say 🙂 I’ll keep you all posted with what I find out next.
We used a different plugin, but next time I run into this issue, I’ll give it a try. Thanks!
The link above shows different code than what I pasted in. I could put the redacted file’s contents onto my google drive and make a public link to it, so let me know if that’s needed. I’ll make sure to use the code button next time; I had intended to, and I think I just forgot.
I’m not using the Theme Editor. I’m modifying the file and uploading via FTP. We have many sites in the same hosting environment and they are not having this issue. There is nothing special/different configured on this site vis-a-vis cPanel.
I, too, always reach for the ftp method. However, when you mentioned the Theme Editor, I looked there, and the version that the above link displays is the version in the Theme Editor. I’ve never seen this before either. Very strange. Editing and saving in the Theme Editor worked where FTP didn’t. So strange.
- This reply was modified 8 years, 5 months ago by jenvander.
Yeah, I saw the errors as well, and the client is aware. I didn’t think any of them were the cause of the style.css issue, but I could be wrong. Did you see any errors that you thought might be related to the style.css issue?
Here is the link to the stylesheet:
https://www.deepwatercay.com/wp-content/themes/DeepWaterCay-Theme/style.css
Here are the contents of the file itself:
[redacted – the link alone is just fine, thank you. Large amounts of code should be linked to, not posted directly]
- This reply was modified 8 years, 5 months ago by bcworkz. Reason: large code excerpt redacted
Forum: Fixing WordPress
In reply to: No changes to my site, suddenly getting errorsUnfortunately, no answer on that forum, and I see that someone else’s post has been languishing for a few days too. Hopefully not abandoned. The theme relies on this plugin, and it’s a paid theme.
I’ve turned off debugging output so the client does not see the errors on the site. I can turn the debugging back on if you need to try something.