Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Warning: getimagesize: failed to open stream #187

Open
3 tasks
brylie opened this issue Oct 11, 2021 · 18 comments · May be fixed by #226
Open
3 tasks

Warning: getimagesize: failed to open stream #187

brylie opened this issue Oct 11, 2021 · 18 comments · May be fixed by #226
Labels
💻 aspect: code Concerns the software code in the repository 🕹 aspect: interface Concerns end-users' experience with the software 🛠 goal: fix Bug fix good first issue New-contributor friendly Hacktoberfest Ideal for Hacktoberfest participation help wanted Open to participation from the community 🟧 priority: high Stalls work on the project or its dependents 🟨 priority: medium Not blocking but should be fixed soon 🏷 status: label work required Needs proper labelling before it can be worked on
Projects
Backlog

Comments

@brylie
Copy link
Contributor

brylie commented Oct 11, 2021 •
edited

When installing this plugin in a local WordPress 5.8 development environment, the following error is displayed when rendering the license:

Warning: getimagesize(http://localhost:8888/wp-content/plugins/wp-plugin-creativecommons/includes/images/by.png): failed to open stream: Cannot assign requested address in /var/www/html/wp-content/plugins/wp-plugin-creativecommons/includes/class-creativecommons.php on line 1128

Steps to reproduce

  1. set up WordPress 5.8 (locally or on a server) in development mode
  2. install the latest version of the code from this repository in the WordPress plugins directory
  3. Go to Settings -> Creative Commons
  4. configure the desired license
  5. make sure to select "Display license as:" "widget"
  6. go to Appearance -> Widgets
  7. add a "Legacy Widget" and select "CC License" widget
  8. save the widget settings
  9. view the site and notice the Warning in the widget area

Task

  • reproduce the issue as described above
  • determine the severity of the notices
  • if needed, fix fhe issue so the notices no longer display
@brylie brylie added 🟧 priority: high Stalls work on the project or its dependents 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix 💻 aspect: code Concerns the software code in the repository good first issue New-contributor friendly Hacktoberfest Ideal for Hacktoberfest participation help wanted Open to participation from the community 🕹 aspect: interface Concerns end-users' experience with the software 🟨 priority: medium Not blocking but should be fixed soon and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Oct 11, 2021
@mimi-tech
Copy link

Hi , I am an Outreachy candidate. I will like to work on this issue. Thank you.

@brylie
Copy link
Contributor Author

brylie commented Oct 13, 2021

@mimi-tech, thanks! I'll assign you to the issue.

@mimi-tech
Copy link

@brylie, Alright, thanks so much

@mimi-tech
Copy link

@brylie, Hope your day is going well?

I have followed the steps mentioned above. I have viewed the site as well. I am using MAMP server but I can't find the error. Can you please give me more guidelines. Thank you.

@brylie
Copy link
Contributor Author

brylie commented Oct 13, 2021

Make sure you have debug enabled in your WordPress installation:

https://wordpress.org/support/article/debugging-in-wordpress/

@mimi-tech
Copy link

Alright, thanks a lot.

@mimi-tech
Copy link

@BjornW , These are the errors I am getting. It is different from the error mentioned above. Please can you explain to me how to solve the error or is it from the way I installed the plugin.
Thank you.

[13-Oct-2021 18:58:04 UTC] called site
[13-Oct-2021 18:58:04 UTC] single site, get site license or else default settings
[13-Oct-2021 18:58:04 UTC] get license for the frontend
[13-Oct-2021 18:58:04 UTC] called site
[13-Oct-2021 18:58:04 UTC] single site, get site license or else default settings
[13-Oct-2021 18:58:04 UTC] called site
[13-Oct-2021 18:58:04 UTC] single site, get site license or else default settings
[13-Oct-2021 18:59:41 UTC] called site
[13-Oct-2021 18:59:41 UTC] single site, get site license or else default settings
[13-Oct-2021 18:59:41 UTC] get license for the frontend
[13-Oct-2021 18:59:41 UTC] called site
[13-Oct-2021 18:59:41 UTC] single site, get site license or else default settings
[13-Oct-2021 18:59:41 UTC] called site
[13-Oct-2021 18:59:41 UTC] single site, get site license or else default settings
[13-Oct-2021 19:05:51 UTC] called site
[13-Oct-2021 19:05:51 UTC] single site, get site license or else default settings
[13-Oct-2021 19:05:51 UTC] get license for the frontend
[13-Oct-2021 19:05:51 UTC] called site
[13-Oct-2021 19:05:51 UTC] single site, get site license or else default settings
[13-Oct-2021 19:05:51 UTC] called site
[13-Oct-2021 19:05:51 UTC] single site, get site license or else default settings
[13-Oct-2021 19:12:50 UTC] called site
[13-Oct-2021 19:12:50 UTC] single site, get site license or else default settings
[13-Oct-2021 19:12:50 UTC] get license for the frontend
[13-Oct-2021 19:12:50 UTC] called site
[13-Oct-2021 19:12:50 UTC] single site, get site license or else default settings
[13-Oct-2021 19:12:50 UTC] called site
[13-Oct-2021 19:12:50 UTC] single site, get site license or else default settings

@brylie
Copy link
Contributor Author

brylie commented Oct 14, 2021

@mimi-tech, I'm not sure what is generating the errors you are seeing. Please open a separate issue for those errors, since they are not related to this issue.

@cillacode
Copy link
Contributor

hi @brylie can i comment on this issue? i replicated the steps and saw the error and its in relation to the issue #186
image

@brylie
Copy link
Contributor Author

brylie commented Oct 26, 2021

@cillacode, great reproduction :-)

Next, we should determine if/how to get rid of the notice.

@cillacode
Copy link
Contributor

Thats fine but i will want to know if the notice has an after effect on the widget functionality, or by getting rid of the notice solves the issue?

@brylie
Copy link
Contributor Author

brylie commented Oct 26, 2021

Those are the questions this GitHub issue is intended to explore.

@cillacode
Copy link
Contributor

I am certain with a better understanding of issue #186 and fixing the notice we can ascertain the after effect of this issue.

@brylie
Copy link
Contributor Author

brylie commented Oct 27, 2021

OK, let's focus on #186 for now.

@cc-open-source-bot cc-open-source-bot added 🏷 status: label work required Needs proper labelling before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Dec 7, 2021
@cc-open-source-bot cc-open-source-bot added 🏷 status: label work required Needs proper labelling before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Mar 13, 2024
@cc-open-source-bot cc-open-source-bot added 🏷 status: label work required Needs proper labelling before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Mar 21, 2024
@cc-open-source-bot cc-open-source-bot added 🏷 status: label work required Needs proper labelling before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Mar 28, 2024
@cc-open-source-bot cc-open-source-bot added 🏷 status: label work required Needs proper labelling before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
💻 aspect: code Concerns the software code in the repository 🕹 aspect: interface Concerns end-users' experience with the software 🛠 goal: fix Bug fix good first issue New-contributor friendly Hacktoberfest Ideal for Hacktoberfest participation help wanted Open to participation from the community 🟧 priority: high Stalls work on the project or its dependents 🟨 priority: medium Not blocking but should be fixed soon 🏷 status: label work required Needs proper labelling before it can be worked on
Projects
Backlog
  
Websites
Milestone
No milestone
9 participants
@brylie @TimidRobot @cillacode @mimi-tech @cc-open-source-bot @ArchanRD @Vickyaryan33 @MrMK0R @71521rav