Meta Box

Hi,

I don't think you are quite right since I have found one possibility.

Turns out you can use composer config --global --editor to edit the local configuration. That way, you don't have to have the license key included in composer.json.

https://stackoverflow.com/questions/54420663/php-composer-global-configuration-private-repositories-url-list

Note: you will need to save and close the file when done like this: https://stackoverflow.com/questions/17535428/how-to-edit-save-a-file-through-ubuntu-terminal.

Now, one can add the appropriate lines to .gitignore to keep things private from the public:

.DS_Store
composer.lock
vendor/meta-box/
vendor/composer/installers/

This works decently, but I still think that MetaBox should update their repositories to support one of the authentication methods described on this page: https://getcomposer.org/doc/articles/authentication-for-private-packages.md. Please log this as a feature request.

Making the repository private is a very strange suggestion considering you have made this: https://github.com/wpmetabox/awesome-meta-box

In any case it sounds like you do not properly support this at the moment. Can you look into updating how the extensions work with Composer so that it is easy for people to keep their license keys private while making it easy to share/collaborate?

Sorry, that was a typo on my end.

I saw no difference when allow_scroll="false" so I was testing to see if allow_scroll="true" did anything differently.

In any case, I do not see this feature working. Can you please confirm on your end that this feature functions when allow_scroll="false"?

@Anh Tran

Do you have any suggestions for this use case? My theme now prevents the user from scrolling the page while the modal is open, but the form submission still scrolls. Therefore, I think I need a solution that prevents MB Fontend Submission from running the animate scroll function that is in frontend-submission.js.

Is there a more robust way for me to override this feature rather than modifying the source code itself? Or, will I need to wait for a new feature to be hopefully implemented first?

Thanks,
Graceson

Hi Long,

I thought about using the template. However, I am making a plugin so I didn't want to use my child theme.

Ultimately, I decided to have my PHP functions set a session cookie to indicate success or failure. When my script runs, it uses the value of that cookie to display the proper message, and then destroys the cookie.

I tried putting the script in rwmb_frontend_after_display_confirmation, however that hook is broken when using AJAX submit on the form. Therefore, I ultimately had to put my script directly in the text of the normal MetaBox confirmation message.

Do you know if that AJAX bug has been fixed yet? I haven't had a chance to test yet, but the changelog for AIO 1.16.7 doesn't mention anything.

Hi Peter,

I know that is the default behavior. Can you share how it works so that I can try to override it?

Thanks,
Graceson

Okay, I understand that the page reloads, and so I can not use JS to print out something. However, I am trying to modify the HTML content of the page to display a message using JS per your suggestion. This is what you suggested:

I think you can use the hook rwmb_frontend_after_process and create some JS code to append the HTML code to the form after processing.

So if the page reloads, how am I supposed to append the HTML? I could write something to the database and then recall it after the reload, but that seems excessive for a task like this. I'm already using php to send the emails that I want. So, I don't understand how I am supposed to use rwmb_frontend_after_process to run some JS that will alter the HTML of the page.

Now, my JS function works perfectly inside rwmb_frontend_before_display_confirmation; however, it appears that I can not use rwmb_frontend_before_display_confirmation inside rwmb_frontend_after_process.

For reference, here is the JS function that I wrote to display the message as desired:

function subscriptionMessage(status = "none") {
  //Wait until the page exists.
  window.addEventListener('load', function() {
    console.log("subscription validation running");
    const mbValidationMessage = document.querySelector(".rwmb-confirmation");

    const message = document.createElement("div");

    if (status == "success") {
      message.className = "rwmb-confirmation";
      message.innerHTML = "Thanks for subscribing to our newsletter!";
    } else if (status == "error") {
      message.className = "rwmb-error";
      message.innerHTML = "Uh oh, we could not subscribe you to our newsletter.";
    } else {
      return;
    }
    mbValidationMessage.parentNode.insertBefore(message, mbValidationMessage.nextSibling);
  })
}