Forum Replies Created

Viewing 15 replies - 31 through 45 (of 69 total)
  • Plugin Author BaneD

    (@baned)

    Hi, OK no worries just wanted to make sure that we get everyone helped ??

    So in terms of the Quick Start. That is actually a way for us to show you the way everything works, and it works with you having the account and without having the account.

    Based on the error it looks like you copied our system generated (temporary) application token that really only works on our website. No worries though we are on the right track.

    Now I will copy paste the steps from above however do read bellow first then come back to them:
    1. Log into your Ziggeo account (US Region or EU Region).
    2. Click on the application you wish to use in the sidebar on the left.
    3. Click on Overview page
    4. On this page you will see Application Token.
    5. Copy that and save in the plugin settings (Ziggeo Video > Settings)

    The first step is the important one as it would allow you to get access to your account.

    Only once logged in would you be able to see your application token.

    Now to support GDPR we have fully separated regions, so you have a log in page for US side: https://ziggeo.com/signin and login page for EU side: https://eu-west-1.ziggeo.com/signin

    You would use one or the other depending on where you account was created.

    Once you log in, go to the steps above and it should allow you to find it. If not, please do reach out to us over email [email protected] (and reference this ticket), or you can also reach out to us through chat in your WordPress website by going to Ziggeo Video > Settings > Contact Us.

    * While no one might be available on the chat when you reach out, someone will reach out to you over email shortly after (do leave us your email you have used to create your Ziggeo account). We can then help you to get the application token in your account.

    Hope this helps ?? With that said, do let me know how it goes.

    Plugin Author BaneD

    (@baned)

    Hi there Karen,

    Might be good for you to open a new thread unless you and beachcalsix are working together.

    Because it seems as if you are connected based on your text, I want to mention that app token is actually important. It is like Google Analytics or Facebook Tracking token that you would place on your website. It is public info however it tells the systems about who it is.

    Just the same, the app token tells our code where to connect to – where to attempt to get the data from or where to send the data to.

    Will change the page to include a link where we explain how to get the token, the easiest way would be to follow these steps:
    1. Log into your Ziggeo account (US Region or EU Region).
    2. Click on the application you wish to use in the sidebar on the left.
    3. Click on Overview page
    4. On this page you will see Application Token.
    5. Copy that and save in the plugin settings (Ziggeo Video > Settings)

    Once added, things will start to work ??

    Of course as always let me know how it goes.

    Plugin Author BaneD

    (@baned)

    Thank you for the screenshots. Based on one of them: https://prnt.sc/tzqnr6 I can tell something is not parsing right on your side.

    Can you send me the link to the page over [email protected]?

    Please do reference: https://www.ads-software.com/support/topic/installation-questions-7/ just to connect the ticket with this right away.

    For more details as you can see
    data-is-gf="true" no_uploadtest

    It means that the field output started, however the no_upload and test got combined for some reason and these are shown because the field already got closed/finalized. This can happen in cases when something “jumps” between the start and end.

    For example when I do the same steps on my side it creates the following error:

    <ziggeorecorder data-id="input_4_1" data-is-gf="true" ziggeo-allowupload="false" ziggeo-theme="modern" ziggeo-themecolor="red" ziggeo-width="360" ziggeo-height="240" ziggeo-timelimit="120" ziggeo-rerecordable="true" ziggeo-tags="wordpress,post,post_152"></ziggeorecorder>

    By seeing the link I might be able to tell more what breaks the code and where.

    Plugin Author BaneD

    (@baned)

    Awesome ??

    In terms of screenshots, none are shown. I am guessing that you might have replied through email and it is not showing them here.

    If you prefer you can send us an email to [email protected]. It is private communication between you and our support team, and images can be included in your email.

    In terms of permissions – yes, you should see the popup that asks you to allow camera and mic to record. If you are using a non HTTPS page, then browser can block the recorder by not allowing flash to work.

    If you are fine sharing the link here, please do, or if you are not, consider sending it in the email to the address I mentioned above.

    In general you should see this as a red icon in the URL bar (often blinking) and depending on your browser by clicking there, you will see option to allow the access to camera or Adobe Flash (only on non HTTPS).

    Plugin Author BaneD

    (@baned)

    I would just like to mention that one image might be missing based on the text in your reply. There is “This is what I see” however nothing afterwards.

    In terms of the empty template field. It should be empty only if you do not pick the template in the Ziggeo template field. Once picked it should work and show you the template you had selected.

    Another reason why it can not show up, would be if you have the template selected and then you remove it.

    When it comes to code, like the one you have mentioned:
    <ziggeorecorder ziggeo-allowrecord=”true” ziggeo-allowupload=”false”></ziggeorecorder>

    This is HTML code and is not actual template code. You could use that however it would need to go into the Gravity Forms custom HTML field. You would then also need a hidden field that would collect the token once submitted and use one of the options to collect it (events or input-bind parameter). The Ziggeo fields however do this automatically.

    In terms of documentation such as videos there is none at this time. Let me see what we can do and have something ready on our website.

    In general what you would do is the following:
    1. Go to the templates editor
    2. Set it all up as you want
    3. Save the template
    4. Go to Gravity Forms builder
    5. Add the Ziggeo Templates field
    6. Set the “Template” option for which template to use
    7. Save the form
    8. Preview the form

    At this point you should see the recorder (or anything the template represents).

    Now with that said, the templates editor has two modes, the simple and advanced editor. The simple only has few options, while the advanced one allows you to add your own code into it.

    Since disabling uploads is not one of the more commonly used options, you would need to use the advanced editor. So copy paste this code into advanced editor field and it will create the code like you mentioned above.

    [ziggeorecorder allowupload="false"]

    * Then click save to save the template and go from step 4 above.

    As you do it should work fine for you ??

    Do of course let me know how it goes.

    Plugin Author BaneD

    (@baned)

    Hi beachcalsix,

    All of our WordPress plugins are made to not be specific / limited to any plan, so it will work regardless of the plan you grab.

    I do want to mention that our core plugin does not include the Gravity Forms integration, and instead we offer this through simple bridge plugin that can be found here: https://github.com/Ziggeo/ziggeo-video-for-gravity-forms

    The core plugin offers most of the code, while these bridge plugins then add something specific to it, like in this case the code for Gravity Forms (so you need both “Ziggeo” and “Ziggeo Video For Gravity Forms”)

    If you add this other plugin, you will immediately see the Ziggeo Fields section in Gravity Forms builder. Within this new section you will see several different fields. This plugin has the hooks and classes needed to make everything work right.

    * Please do note that the plugin is only available through Github for now.

    If you prefer, you could use HTML code and the Gravity Forms HTML field to add the integration directly, however the above plugin is going to make things easier to set up if you are not familiar with the code.

    Do check it out and let us know how it goes.

    Regards,
    Bane

    Plugin Author BaneD

    (@baned)

    Hi,

    Just wanted to mention that I will close the ticket, however please do feel free to open a new one if there is anything else that we can assist you with.

    Also if you like our plugins, please do consider leaving a review ??

    Regards,
    Bane

    Forum: Plugins
    In reply to: [Ziggeo] Fluent Forms
    Plugin Author BaneD

    (@baned)

    Hi there,

    Just wanted to mention that I will close this ticket however please do open a new one if you have any additional questions.

    Also if you like the plugin, please consider leaving a review ??

    Cheers,
    Bane

    Plugin Author BaneD

    (@baned)

    Hi there,

    The issue was caused by a change in the Ziggeo core plugin that was created to make less code loaded on any request. Unfortunately it was missed that bbPress was using one of the functions that was within those files. These functions would however outside of bbPress only be used within the admin side.

    The issue was reported shortly after release and immediately updated. If you were to update the core plugin you will immediately see it all working.

    Please do let us know of course how it goes.

    Forum: Plugins
    In reply to: [Ziggeo] Fluent Forms
    Plugin Author BaneD

    (@baned)

    Hi,

    Just wanted to let you know that we have made the integration into Fluent Form. You can get your code for it here: https://github.com/Ziggeo/ziggeo-wp-video-for-fluent-forms

    Please note that for now we will not be uploading it to WordPress repository. We are looking to have several people letting us know that they would like the plugin to be in WordPress repository to move it there.

    This would allow us to push out the integrations out and help our customers as well as to keep WordPress team happy as we post addons that our customers show interest in keeping in WordPress.

    Our core plugin does include Addons page that we will build up upon at which point it would be the place where you will have the option of marking the ones you use and wish to have on WordPress ??

    Hope this helps and please do let us know how it goes ??

    Plugin Author BaneD

    (@baned)

    Hi,

    Thank you for leaving your feedback in the form of this review.

    You just wrote “pricey” so I do wish to mention that this plugin is free.

    If you have any questions about setup, what this plugin is about or you wish to contact our sales team, please do let me know and I would be happy to assist you with the same.

    Thank you.

    Plugin Author BaneD

    (@baned)

    Hi,

    Wanted to let you know that the do_shortcode is now supported by the latest 2.4 version that is out now. You will see that there are few other changes added to it as well.

    I do wish to thank you for the wait and please let me know how your tests go with the same.

    Regards,
    Bane

    Forum: Reviews
    In reply to: [Ziggeo] NEEDS TO BE FIXED!
    Plugin Author BaneD

    (@baned)

    Hi there,

    Thank you for the interest in the plugin and for taking time to leave a review. I do wish however that you have contacted us so that we can gather more details on the error as well as the link to where we can check it out.

    With that said I also do want to mention that the plugin is free. The plugin brings Ziggeo to WordPress and Ziggeo plans start with a free plan and goes through 99 per month, 399 per month and higher.

    Now based on what you said I am not sure where the issue is. Seems that you have used Ziggeo core plugin as well as video walls plugin, however you also say that after installing it broke your website.

    We are about to release a new version which works fine for latest WordPress version however would be happy to check into this and make sure we include any issue that is causing this for you.

    To do this, can you please try installing / activating the plugin one by one. 1. Ziggeo core plugin https://www.ads-software.com/plugins/ziggeo/
    2. Video walls plugin https://www.ads-software.com/plugins/videowalls-for-ziggeo/

    When you install the core plugin, can you go to Ziggeo Video menu and confirm settings working for you. Then afterwards install / activate the videowalls plugin.

    If you can tell us what error you get and after what steps, together with the info about your WordPress version we should be able to get more details and help you get set up.

    Regards,
    Bane

    Plugin Author BaneD

    (@baned)

    Hi there,

    I added the codes for this and tested against few of my tests to make sure all seems to be running fine.

    The goal is to finish the latest changes I was working on and then test it all and release as the new 2.4 version of the plugin. I would also be testing everything against WordPress 5.4.2.

    I am happy to give you instructions and codes you would need to add to add the shortcode support manually (until the update is released). That way you can continue working on things on your side or if you are OK to wait few days, we will be making a new update that adds the shortcodes support as well as few new things ??

    Best,
    Bane

    Plugin Author BaneD

    (@baned)

    It does not seem that we support do_shortcode() at this time, it is something that was added to the list to add, however never really needed.

    I am going to check the codes and jump on my keyboard for a bit to see what happens :). Should be easy to add however I do want to make sure that it works the very same way as the non shortcode parsing.

    What currently happens is that we are parsing the content itself for any shortcodes within it, however not through actual do_shortcode functionality. That way we support older WP versions in many more locations than what we would if we implemented the do_shortcode approach as usually.

    Bane

Viewing 15 replies - 31 through 45 (of 69 total)