kerryoco

ah thanks. It seems to be picking up the differences between files with different letter-cases in the filename, so it’s actually ok. (PLAYER.js, and Player.js). The browsers treat those as separate files but Wordfence isn’t. I’m not sure exactly why your Wordfence is showing that but mine isn’t (I have it installed on a bunch of sites too). I’ll make a note to modify the filenames with the next update to avoid the warning though.

Do you host on Windows by any chance? If I remember correctly, Windows doesn’t use case in filenames, and if Wordfence is somehow using the OS for filenames, that might be related, and something I should think more about as well

• This reply was modified 1 year, 8 months ago by kerryoco.
• This reply was modified 1 year, 8 months ago by kerryoco.

I got inspired and went ahead and did this today. You can find the new Global Settings tab in the Threepress menu item. I’ve tested it on 3 sites now; let me know any issues.

Sorry it’s probably an issue with the Threepress HDRI implementation; it was never completed as fully as it should have been. You can implement your own using the same method that you would add your own GUI, but if you check out the docs for HDRI in threejs you’ll see it’s very finnicky to get right.

The GUI is a little easier. I was planning at some point to allow custom js adds, but in the meantime, you can use a plugin like Header Footer Scripts to inject your own. First add that CDN link to the dat.gui script. And then also add a script of your own. If you can, find another way to test, even if it’s just running the script in the console, to make it go faster. If you get the dat.gui included on your site, I could even do a sample of the rest on your page probably.

Blender is best for exports yea. Latest versions have glb convert / export built in, and I’m not an expert on the various settings, but most material export settings are available in the export dialogue.

For the parameters, you probably want this mini library. It’s the same you saw earlier – “dat.gui”.

You make “a GUI”, “a folder”, and then when you tag / add the properties in they become available automatically as inputs if I remember correctly.

Aha, good to know the cause at least. I don’t think there will be any fix other than disabling that particular one. The issue is Threepress uses unbundled js modules. This is an increasingly used practice, but for it to work with these optimizers I would need to bundle all the Threepress routes into separate bundles, and I likely won’t have time for that.

If you need any help getting the parametric stuff started feel free to ask.

I just tested out those 3 components on one page too, and so far it seems ok.

https://oko.nyc/threepress-samples/

CFF plugin, with a chart.js Chart, and Threepress galleries. Only difference may be that my Chart is not generated by CFF; I’m not familiar with that route. I was just working with Chart.js myself anyway though so I included one from scratch.

Can you view your javascript console for errors ? If there’s no red messages there you can try installing ‘Error Log Monitor’ to get a log of PHP errors.

Hi, was the plugin turned off for some reason perhaps? The shortcode that you’re seeing there should be getting converted into data if the plugin is active, so it should never even appear in the HTML (it’s not sensitive data though).

My only other guess would be that the plugin is encountering an error in trying to parse the shortcode when you load the page, but I’m only saying that because this would be the fallback output. I don’t have a guess as to what the error actually would be. You can install the plugin “Error Log Monitor” to display errors in your Dashboard as you try to load the page, and if you see the name Threepress in there then let me know.