Do you need min and max FOV values for each scene, or global virtual tour settings? I think it’s best to use global settings, but also allow them for each scene, if a scene has its own values, they will take precedence over the global ones. They will be disabled by default. Ok, I will add this options this week, after the embed iframe feature.
Hello. The plugin does not currently support this. However, I can implement this feature in the next version, likely by tomorrow, as it is a minor change.
P.S. I’d be happy to hear any suggestions regarding features you’d like to see in this plugin.
About marker size. You should set the custom css class for the marker
Then define styles in the custom css section
P.S. Also, please note that I currently provide support for this plugin only for critical bugs. At the moment, I’m actively developing a more advanced alternative: HappyVR. It’s in active development and already available here: https://wordpress.org/plugins/happyvr/
I’d be happy to hear any suggestions regarding features you’d like to see in the virtual tour builder.
The issue is most likely related to caching, an old configuration is being loaded (either on the server side or in the browser). I recommend checking the page’s HTML markup, specifically the block containing the panorama. It’s possible that it contains an incorrect ID. It would be helpful if you could send a screenshot of that section of the HTML code.
Also, please note that I currently provide support for this plugin only for critical bugs. At the moment, I’m actively developing a more advanced alternative: HappyVR. It’s in active development and already available here: https://wordpress.org/plugins/happyvr/
I’d be happy to hear any suggestions regarding features you’d like to see in the virtual tour builder.
Hello. In principle, the plugin should work on earlier PHP versions as well, since it doesn’t use any features exclusive to the newer PHP releases. However, I’ll test it thoroughly and update the compatibility within the next few days, provided everything works as expected. Thank you for reaching out.
I’d like to clarify that the subfolder functionality was never part of the free version, it has always been a Pro feature, as is common with similar plugins. That said, upon reviewing the description, I acknowledged it could have been clearer, and I’ve already updated it to prevent any further misunderstanding.
I’ve invested significant time and effort into building a reliable, well-reviewed product that delivers real value at the lowest price point. You can verify this by checking its listing on my CodeCanyon profile.
If you ever have questions or need assistance, our support forum is open, and I personally respond to every request.
That said, while I welcome constructive criticism, comments like “Not Goodman” cross the line into personal disrespect. Such phrasing doesn’t foster productive dialogue and overlooks the dedication behind the product.
I appreciate your understanding and hope you’ll reconsider your review in light of the updated description.
@kozynets It’s not very clear where the ‘,attachment,,0,‘ part comes from. Could you please share a screenshot?
If we’re talking about CSV, then commas (,) are delimiters, and the first line defines the column headers. The attachments field contains a string like 26|27|28|29|30|31|32|33|34|35|36|37|38|39, where IDs are separated by the pipe symbol (|).
I’m a bit confused about the files. As you can see, the final CSV has an “attachments” column, that’s exactly the files attached to the directory, specifically their IDs and the actual files themselves should already be present in the destination WP database.
There is one way, but I’ll need to make some minor adjustments to the import functionality, as the current implementation (iFolders v.2.9.0) turns out to depend on the order of folders in a csv file.
In this case, however, you’ll only be able to import the folder tree structure without attachments linked to those folders.
