felipelungov

No more warnings with the development version. Already updated to the newest version that I see also includes this fix. Thanks @gabelivan !

Thanks! Just uploaded the development version, will check on Monday if I’m still getting those warnings.

Thanks for your reply @gabelivan .

Here is what I have for CSS:

/plugins/wd-instagram-feed/(.*?).css

For JS:

/plugins/wd-instagram-feed/(.*?).js

I guess we found the culprit. I’m removing those lines for now as I’m not even using that plugin.

same here

Thanks, Alvaro. I just realized my title wasn’t very descriptive, and I can’t edit it now. Feel free to change it.

Wow, that was fast responding! Thank you!

I just updated, I’ll let you know if I get any more of those notices.

Sorry, I opened the thread here because I thought these were your classes, especially since I had just activated your plugin. I will look further into it.

Wpil_Base
Wpil_Suggestion
Wpil_Settings

Are you sure that there are no remaining artifacts from a previously activated WPML in the database?

There may be.

Happy to give you any more required information, of course!

No worries! Thank you!

Hi Jordy,

I saw that you released a new version on Jan 31st, but you didn’t include this fix. Do you think it will be merged into the code soon?

Thanks!

Hi,

Yes, I’m sure it was happening at darfyx. I was away on holidays, and now I am back and that message is no longer showing up. The last Polylang update I have recorded was on Jan 16th. Could it be that some other theme/plugin is/was using the same variable names such as $links, $slug or $lang?

Anyhow, things look all right now. But I’m keeping an eye out. ; )

Thanks for your support!

I’m using the standard switcher. Here is where it happens:

https://darfyx.com

I can pm you admin credentials if you think it might help.

Sorry, I just realized that the forum chopped the post title which contained the complete error message. Here it is:

Notice: Trying to get property 'slug' of non-object in /home/user/public_html/wp-content/plugins/polylang/include/switcher.php on line 61

I unfortunately don’t have the tools to provide you with a stack trace.

Hi, after I messaged you I realized that switching to the MySQLi storage engine has caused an even greater amount of notices in my logs, so I switched back and I am now looking for a new hosting company where I can better control file permissions.

Will do for sure!

Regarding the fix, it has been over 24 hours with no errors or notices from your plugin, so I think it is now safe to say that we have a fix!

Thanks for your support. I will contact you regarding access to the repository.