Im trying to publish a challenge on frontend mentor using Git Hub.
When i try to use the live url, images dont show up.
Ive tried PNG, paths and some more things i saw on the Internet but ,for now, nothing has worked.
Live Url:https://pires29.github.io/First-Project/
GitHub Page:https://github.com/Pires29/First-Project.git
(Could put the code in here)
img src="image-qr-code.PNG"
Check your path.
Your images should be on the public file and your path must looks like /<imagesFile>/image.png
Greetings & Salutations one and all
I'm new to mixxx been using it for about 4hrs and its a brilliant piece of software so thanks once again for this amazing program. The issues i'm having is that it creates and double m3u.m3u. extension when I'm live broadcasting. I had issues with getting this to work but figured it out with lame.dll which I didn't have to rename as this solution is for version 1 and below.
It works now after putting the lame encoder.dll file into the mixxx folder, which I think might be the issue i'm not sure. the live broadcasting connects successfully and it connects to my icecast server without issue, however when I click on m3u on icecast admin page or connect directly to it the web e.g. http://externalIP:8000/stream it show me the m3u.m3u error, which is causing the streaming error as its creating a double m3u file and as we know only .m3u works not m3u.m3u. so I think its the encoding creating this double extension but I'm not sure hence the post. any ideas??
mixxx m3u.m3u error
Make sure you configure a mount point in Mixxx.
Like /stream.ogg or /radio.opus, depending on the format/codec.
Also make sure that it does NOT end in m3u! The mountpoint is a virtual media file, not a playlist. The server will automatically generate another virtual file, a m3u playlist for it.
I want ot create a release for my Github project, but when I try to upload my binary (which is a .zip file) to the release, I get the following error message:
Something went really wrong, and we can’t process that file.
I get the same error message if I try to upload some other files (e.g. my readme file). What could be wrong?
Check first if this issue persists with all browser.
I have seen this error message before, where the upload succeeded with Chrome, but not Firefox.
For the record in my case this was due to an obvious mistake: I had to authorize a github script in NoScript.
If someone encounters this problem in China, and is using ShadowSocks, try turning ShadowSocks off.
I was trying to upload an image file in png format on chrome browser but I was getting the same message.As suggested in one of the answer, I turned off windows firewall and it worked.
But my mind was not satisfied and I turned on Windows firewall and converted that image to jpg format and it got uploaded.
But this stubborn mind was not satisfied and told me to upload this in .png format only.God came to my rescue and accidentally properties tab of png image got opened and at the bottom of tab, it was showing
"This file came from another computer and might be blocked".
So I unblocked it and it got uploaded.
I got that error due to my companies firewall that prevents all file uploads. Might this be the cause of your problems?
The problem occurs during file upload because I was using VPN which doesn't allow file upload hence I disconnected from VPN and then try uploading which work absolutely fine. So my advice to check your firewall/VPN settings as mostly Organization doesn't allow fileupload in GIT due to security concern.
I got the same problem on Opera browser(Ubuntu 18.04.1).
Then I realized that my browser does not have permission to access the related(where your files located) partition. I moved the files that I wanted to upload on Github into accessible partition by Opera browser in my HDD, Thus I could be able to upload my files to Github.
It worked like a charm. Hope this helps.
clear your browser's cookies and cache ..after clearing files will be uploaded easily on git without error
In my case. I'm reuploading two zip files to an existing release. One success and another one failed. Tried in both chrome and firefox.
My solution is to use the hub command-line tool.
I use the below command to edit the existing release and attach files to it.
hub release edit --draft=false --attach FILE TAG
For some reason, I had to change its prefix from .png to .jpg and it worked.
I had the same problem which I solved by disabling my firewall. I hope this will work for you
In my case, it was my anti-virus (AVG) preventing the upload.
In my case, Avast antivirus was blocking the objects-origin.githubusercontent.com site, and made the upload fail.
After disabling the antivirus, I was able to upload the files.
Well! That is because your are uploading some images that you have downloaded from the internet like in my case I have used a favicon that is generated from website to solve the issue Image with security details~img1
Image with detail~img2
Remove personal info ~ img3
To solve the problem
first of all head to the images that you have downloaded from internet and right click on image and click on properties
check the unblock checkbox as shown in image 1 and then
click on the details tab as shown in image 2 and then click on the remove properties and personal information
And then check on the remove the following properties on the file as shown in image 3
And then click on ok and then again ok
The given solution will solve your issue it just worked perfect for me
Files cannot be uploaded because your network provider doesn't allow, use different network or apply vpn for uploading the files.
I don't manage to get the Image Tools plugin to actually upload the images to the server. I upload images with the jbimages plugin with no problem. But when a picture is edited with the Image Tools, although there's the uploading bar, which gets to 100%, it seems that it's only uploaded as a blob. The page calls the tinymce.activeEditor.uploadImages() function when submitting the form data, but it doesn't work.
I use the 'postacceptor.php' file from the example (defined in 'images_upload_url') and the 'images_upload_base_path' is defined as well.
The files are not uploaded to the server, and the img src remains a blob.
What could the problem be?
Thanks!
What debugging have you done in your PHP code? Is the code being triggered? Does the file appear in the posted content? You need to narrow down where in the process things are failing.
Is the issue that TinyMCE is not posting the edited image or is the issue that the image is posted and the PHP code is not properly saving the image and returning valid JSON?
How did you configure TinyMCE?
Does an edited image get posted to your server code?
What is in that form post?
If you disable the jbImages plugin does that change anything?
Without more details it will be very difficult to help you figure this out.
I have recently started working with a fresh install of FMS 4.5.0 and am having some issues getting my media to load with the VOD application.
After uploading some of my own FLV/F4V content to "/webroot/vod/", I am currently only able to load the samples from the installation.
Is there some sort of configuration that needs to be made to access my media?
Do I need to create a manifest for each video?
I have been running tests through:
http://www.osmf.org/configurator/fmp/
And have had luck accessing the videos that came with the install by using the following:
Video Source (URL): http://[my host]/vod/sample1_1000kbps.f4v
But when I change this to point to one of my recently uploaded videos it fails everytime.
Another strange note, I was able to play one of the samples but then I changed its name and it was still able to load that one specific video using the same filename when the file's name had changed. This leads me to believe that it isn't really loading the right files or perhaps I am uploading to the wrong directory. But I can't find any other directories that have video in them.
Please let me know if there is any more info you need to help me. I'm fairly new to this and am not sure what to include.
Thanks in advance for any help!
EDIT: This was a pathing issue.
This has been resolved.
Apparently my webroot directory for the server was not set up correctly and after it was pointing to the right directory it was fixed.