Minecraft Forums

Quote from EM3R50N»

Just to confirm - those of us who are setup on CurseForge are not able to use modifiers like "1.7.10", "latest" etc? I've tried and doesn't seem to work for me.

As long as the content is available on curse.com then the modifiers should work, you can append ".json" to any widget URL to see exactly what data the widget has available. Here's your latest mod data: http://widget.mcf.li/mc-mods/minecraft/244453-logical-drops.json

I think the problem you've ran into is that the data on the widget is cached for up to an hour, meaning when you add a new file you may need to wait for up to an hour before the widget knows it's there, here's your latest mod with version 1.7.10 specified:

[mod="1.7.10"]244453-logical-drops[/mod]

The presence of the cache can be quite confusing at first, it's a problem I'm looking to address long term Please let me know if you need any further help.

Quote from MCenderdragon»

Is there a way to implement a latest option ? like [mod=latest]#curse_numbers[/mob]

Latest is supported, it's the default. Are you having issues with not seeing the latest file? Have you uploaded a new file within the last hour? There is a cache that is cleared once an hour.

Quote from MCenderdragon»

Yes, it displays the latest stable file. But it would be also nice if it is possible to display alphas or betas.

Ah I see. The widget does support beta files, however it does not support alpha files, this is because curse.com does not list alpha files, only beta and release, alpha are only available via curseforge. Sorry for the inconvenience

Quote from MCenderdragon»

ok then if i just write [mod]#modid[mod] will it the display the stable 1.7.10 version or the 1.8 beta ?

The default is the latest file marked as release (stable), so in your example the BBCode would display the 1.7.10 stable version. You can specify a release type, eg: "beta". Here's a few examples using Futurepack of how you could use the widget:

This will display the latest file marked as Release, in your case that's Futurepack (v22.2.69)

[mod]237333-futurepack[/mod]

This is equivalent of doing:

[mod="latest"]237333-futurepack[/mod]

[mod]237333-futurepack[/mod]

This will display the latest file marked as Beta, in your case that's Futurepack (v22.2.55)

[mod="beta"]237333-futurepack[/mod]

[mod="beta"]237333-futurepack[/mod]

This will display the latest file marked as Beta for version 1.8.9, in your case that's Futurepack (v22.2.55)

[mod="1.8.9/beta"]237333-futurepack[/mod]

[mod="1.8.9/beta"]237333-futurepack[/mod]

Please let me know if you need any more help, I hope this is clear

Quote from WhichOnesPink»

Hello -

The widgets have been working great on the main RTG thread, but recently they seem to have broken. Inspecting the console in Chrome reveals this error for every widget on the page:

Blocked script execution in 'http://widget.mcf.li/mc-mods/minecraft/237989-realistic-terrain-generation?version=1.7.10' because the document's frame is sandboxed and the 'allow-scripts' permission is not set.

Looking at the HTML, there does indeed seem to be a 'sandbox' attribute on the <iframe>, but I don't know if it just started appearing, or if it's been there all along.

Any ideas what might have happened here?

[Edit: Imgur galleries also seem to be producing a similar error.]

.

Thank you for the report, I'm looking into this with the development team. I'll let you know as soon as I know more. Please can you let me know which version of Chrome you're using on what operating system. Thank you.

Quote from WhichOnesPink»

Running Windows 10.

I was on Chrome version 50.0.2661.94 m when I made that post, but when I checked for the version number in Help > About, it updated to version 50.0.2661.102 m (both of which are still throwing the error unfortunately).

I can also confirm that Firefox is affected, using versions 45.0.2 and 46.0.1

Let me know if you need any additional information.
.

Thank you for the information. The issue has been identified and I'm working with our development team to resolve the issue. This is specific to the forum and does not impact the widget itself or CurseForge, in the mean time you may wish to swap out your widget embeds for direct links to the CurseForge page, then once the issue is resolved you can use the Post History option to rollback to the version of your post with the widgets included. I'm sorry for the inconvenience this is causing, I'll let you know as soon as it's resolved.

Quote from WhichOnesPink»

Running Windows 10.

I was on Chrome version 50.0.2661.94 m when I made that post, but when I checked for the version number in Help > About, it updated to version 50.0.2661.102 m (both of which are still throwing the error unfortunately).

I can also confirm that Firefox is affected, using versions 45.0.2 and 46.0.1

Let me know if you need any additional information.
.

Thank you very much for your patience, this issue has now been resolved. The issue was caused by a security change, all iframes were updated to be sandboxed, unfortunately sandboxed iframes are unable to execute Javascript or open new windows, the widget depends on opening a new window when a download button is clicked.

A fix has been rolled out and the widget is now working again in all posts, no action needs to be taken. The threads impacted by this issue are those that contain a widget and were edited in the last week, there are 30 total threads that meet the criteria, I am reaching out to each individual author to let them know about the issue.

Once again I'm very sorry for the inconvenience caused, I hope we haven't had a negative impact on your content due to this bug

Quote from WhoStoleMyNameFrWhy»

it may be because my mod just got approved but i cant seem to get the widget to work it just say that my mod that i can see approved and on the curse website, dosn't exist. can you help me please?

Your project does not contain any files marked as release or beta, your project online has one file marked as alpha. A project with alpha files only won't be available on mods.curse.com which is where the widget gets its data from. You'll need to add a beta or release file. I hope that clears it up, let me know if you need any further help.

Quote from MCenderdragon»

how is it sorted? is it sorted by upload time or by minecraft version? currently the normal [mod] tag displays the 1.9 but I already have an 1.10

If you don't specify a version or a file type then the widget will pull out the latest file uploaded, you can override this by specifying a version. The mod in your signature should show the 1.10.2 file if you don't specify anything as it's the latest file uploaded.

You can access the data the widget uses directly by appending .json to the widget URL, eg: http://widget.mcf.li/mc-mods/minecraft/237333-futurepack.json

Let me know if you need any more info or clarification

Quote from csb987»

Has the removal of mods.curse.com killed these widgets permanently, or will they be fixed? Is there anything that people who've added widgets to their threads need to change to make them work again?

I was unfortunately provided with no notice about the upcoming change to mods.curse.com, meaning I have just found out that it has broken the widget. I am now looking at the next steps forward for repairing the widget, however at best it will be a couple of days before the widget is up and running again, possibly longer, and depending on some things that I'm waiting to hear back about, it's possible some widget embeds will be permanently broken. This is an unfortunate situation that I am very sorry for and will keep this thread updated with information.

I have released an emergency patch to update the widgets to provide a more informative error message, and a link to the new curseforge page for each mod, however, due to broken redirects these links aren't guaranteed to work. This is what viewers will now see:

Widget currently unavailable
Error Due to breaking changes at the curse.com website, this widget is currently available. Please visit the project page directly at: https://mods.curse.com/customization/minecraft/229041-lucky-block-spiral-1-8-lucky-block-addon Please email [email protected] with any questions..
The widget requested cannot be rendered.

Quote from csb987»

Has the removal of mods.curse.com killed these widgets permanently, or will they be fixed? Is there anything that people who've added widgets to their threads need to change to make them work again?

FYI the widgets are back online now. Let me know if you run into any issues. Thanks for your patience!

Quote from MCenderdragon»

I uploaded a new file for my mod 2 days ago, yet the complet API behind the widget and the widget itself is stil not listing this file nor changing the link to this file. Are there any issues with curse or the updates ?

Sorry about that, looks like there's a bug. I'll investigate on Monday and provide an update for you. Thank you for your patience.