Highcharts export - Where is the index-utf8-encode.php file - highcharts

I'm using highcharts in many projects. When I configure exporting option, I always use "index-utf8-encode.php" because it support other charset than UTF-8 (ex: ISO-8859-1).
exporting: {
url: 'http://export.highcharts.com/index-utf8-encode.php'
}
Unfortunately, since weeks or months (not sure exactly when) when I try to export graph to an image file I get a 404 error from a tomcat server.
See (and try to export as image file) : http://jsfiddle.net/yWLwx/126/
So, is there someone who knows where is the index-utf8-encode.php file or why it doesn't work anymore?
Thank you very much for your time!!


Please familiar with our php exporting servers https://github.com/highslide-software/highcharts.com/tree/master/exporting-server/php
It is caused by changing export server.

Related

Using OpenElement to open an Attachment with a URL

Trying to open an attachment with this url and it doesn't work. Any idea why?
https://Blah-apps.com/Development/StrongB.nsf/0/(Attach)/0/B3B9D4480BEF667C852588310078E1AE/$File/golf.pdf!%20&OpenElement
Thanks for any ideas
The attachment was originally created on the web and was an embedded object. I then wrote code to move it to a Rich Text Field and that didn't help. The error I get is
HTTP Web Server: Couldn't find design note

This is from a note that I pulled together for HCL some time ago listing the issues we had with Domino 11 having upgraded from 9. This might help although it is not clear what version you are on.
Broken Download links for LZ1 compressed attachments. - CS0313452
After upgrading to FP5 customers found that they could not download some attachments.
We were able to reproduce this issue 100% and provided HCL with a database.
https://eon.focul.net/eon/apps/moc.nsf/xp_f_mod.xsp?action=openDocument&documentId=67BC79B86B06BAFD802582B30042ACFB FoCul determined that this happens to attachments that are automatically compressed with LZ1 even when the database settings do not enable compression.
+SPR# GRHEBVYNW7 - Server - DAOS - Fixed an issue where after upgrading to 11.x,
running dbmt -c on DAOS enabled databases results in duplicate DAOS objects being stored.
This regression was introduced in 11.0.
The URL syntax affected is the old style https://<>//<>/<database.nsf>>/<>/$FILE/<>.jpg
whereas the newer “XPage”style syntax works fine
We modified our applications to use the XPages style syntax as a good work around.
This is the XPages url style
https://acme.focul.net/apps/moc.nsf/xp_f_mod.xsp?action=openDocument&documentId=67BC79B86B06BAFD802582B30042ACFB

Your use of /0/(Attach)/0 looks wrong. Try this format instead: http://host/Database/View/Document/$File/Filename?OpenElement (source: https://help.hcltechsw.com/dom_designer/9.0.1/appdev/H_ABOUT_URL_COMMANDS_FOR_OPENING_IMAGE_FILES_ATTACHMENTS_AND_OLE_OBJECTS.html)
So in your case:
https://blah-apps.com/Development/StrongB.nsf/0/B3B9D4480BEF667C852588310078E1AE/$File/golf.pdf?OpenElement

Uploading Google extension to Microsoft Edge Add-on Store - _MACOSX error

I'm using a mac to upload my extension (which can upload fine to the google chrome extension store)
Is the Microsoft Edge store the same? Should I do anything differently?
I just tried to upload the exact zip file and I'm getting these errors.
Sorry in advance, this is probably a noob question. I have zero experience with the microsoft edge store so I'm not even sure if they allow/make possible to upload from mac? (assuming this from every error containing _MACOSX error)
Here's the error in text format
The following checks failed:
Package acceptance validation error: Files or directories outside directory that contains manifest.json chromium are not allowed: __MACOSX, __MACOSX\._chromium, __MACOSX\chromium, __MACOSX\chromium\._.DS_Store, __MACOSX\chromium\._background.js, __MACOSX\chromium\._geo.js, __MACOSX\chromium\._index.html, __MACOSX\chromium\._main.js, __MACOSX\chromium\._manifest.json, __MACOSX\chromium\._popup.html, __MACOSX\chromium\._popup.js, __MACOSX\chromium\AutoStuff, __MACOSX\chromium\css, __MACOSX\chromium\img, __MACOSX\chromium\js, __MACOSX\chromium\_locales, __MACOSX\chromium\AutoStuff\._insert-auto-message.js, __MACOSX\chromium\AutoStuff\._shared-basic.js, __MACOSX\chromium\AutoStuff\._shared-website.js, __MACOSX\chromium\css\._.DS_Store, __MACOSX\chromium\css\._jquery.toast.min.css, __MACOSX\chromium\css\._popup.css, __MACOSX\chromium\css\._style.css, __MACOSX\chromium\img\._.DS_Store, __MACOSX\chromium\img\._icon-128.png, __MACOSX\chromium\img\._icon-1280x800.png, __MACOSX\chromium\img\._icon-16.png, __MACOSX\chromium\img\._logo.png, __MACOSX\chromium\js\._jquery-3.4.1.min.js, __MACOSX\chromium\js\._jquery.toast.min.js, __MACOSX\chromium\_locales\._.DS_Store
Edit: I wonder, do I need to format the zip file differently?

I try to search for the error your package failed certification. make corrections and certify again.
I found that other people had a similar issue before. I suggest you try to reupload the package. See if it uploads successfully. If the issue persists then there may be some other issue with the package or extension.
You said you are trying to upload the exact same zip file to the MS store. You may need to port your existing Chromium extension to Microsoft Edge
You can refer to this docs may help you to know the process to publish the Edge extension to the MS store.

I had the same issue and got over it by using the shell to zip it:
# remove MacOS' .DS_Store file
rm ./my-edge-extension-folder/.DS_Store
# zip the extension
zip -r my-edge-extension.zip ./my-edge-extension-folder

YAWS crash uploading 7 MB file

I'm using a Raspberry like board with YAWS 2.0.4 and Erlang 19.
I wrote two webpages to upload a file and save it on the server: with "larger" file (I mean, ~7MB) the server crashes, with smaller file all works fine.
I already tried to use the example code found in the YAWS site and another one with the temp_file and binary options, but it doesn't work.
Any suggestions?
Thanks in advance.

After spending much time, I've found the problem: the partial_post_size parameter in the YAWS configuration was too much high.
I've changed it, near the default value (10240) and all works fine.

Highchart offline export for pdf file not working

I am using the latest High-stock , exporting and offline-exporting java script file for my angular application. When I use the highstock api "exportChartLocal" in my code as "chart.exportChartLocal({type:"application/pdf"});", I can able to download for png,jpeg and svf format.But I am not able to get the pdf format displaying as "file damaged".Can anyone help me solve this issue?

Unable to Export HighCharts from IE

When I export my graphs from IE, the exported file is not coming up with a file extension.
This was working until a couple of days Ago.
Has anyone else seen this behavior? is there a fix for this?
i am able to export fine from Google Chrome.

This is fixed and working now for the public export server.

Resources