Plugin Toast Notification - Toasty Free/Pro

Showcase
21

Can you simply create a new app, and test it?

22

I did, and works on new app, also installed same plugins as main app and works on the new one. I mean thereā€™s something is doing conflict but i dont figure what is. I copy-pasted most of the things of the main app and nothing

23

Good news :wink:
Uninstall all plugins but the one, and test it. Until you find the conflict one.
You can destroy all your app piece by piece than restore it at present date time.

24

Iā€™m noticing this issue on bunch of plugins off late. Are other plugin builders noticing it too ?

25

For me it was causing issues because I had custrom script related to the first version of the signature pad (when it wasnā€™t a plugin)

Canā€™t remember what js library it was but it was in my headers so not a pluginā€¦

26

I have the Pro versionā€¦ Have copious amounts of plug-ins and also page specific scripts. I havenā€™t seen any issues. Just an FYI

27

Hey guys I just want to remind everyone that the pro version has a completely different core. If anyone whatā€™s to test the pro version on there app please DM me

1 Like
28

@AliFarahat I have the Pro plugin and have done for some time. Iā€™m getting an error in the console stating that itā€™s not authorised?

Thanks in advance

29

Can you share a screenshot, please. Is tyhis new?

30

Hi @AliFarahat, the more I use it, the more I love toasty!

One feature request though: could you add dynamic data to the ID field?
image

This way I can reference (for example) a repeating groupā€™s index and show the toast msg at the correct entry!

Thanks!

2 Likes
31

Glad itā€™s useful. I will make the changes you and let you know

2 Likes
32

Hey Ali,

I get this error when trying to reference the current cellā€™s index:

image

image

Any idea what it could be? Maybe because it adds #?

33

I think so. Can I see the editor so I can debug and fix?

34

yeah, whenever you have time you can jump on my appear.in channel and I can show you! Thanks!

When I look at the attribute, it says just simply the number, it doesnt add # so not sure!

35

In CSS, identifiers (including element names, classes, and IDs in selectors) can contain only the characters [a-zA-Z0-9] and ISO 10646 characters U+00A0 and higher, plus the hyphen (-) and the underscore (_); they cannot start with a digit, two hyphens, or a hyphen followed by a digit.

Place a static letter in front of the cell index expression, this should sort it out.

@AliFarahat, if you need to use element idā€™s in your plugin code you can get around this issue with something like,

$('#myPlugin_' + properties.id).something();

Just make sure you keep that same static '#myPlugin_' rather than '#' through your code and then users can reference a cell index or other number without the selector issue.

2 Likes
36

Thanks Jarrad, Iā€™ll try this. I tested ā€˜formatted asā€™ but forgot to test witch a character in front. Iā€™ll try when Iā€™m back at it!

37

Thanks for the tip @jarrad I will run through the code now and update where necessary

38

Hey @jarrad & @vincent56

It looks like i cant really make these modifications as I am targeting your specific element and not something with in the plugin it self.

@jarrad
The code here looks like this

var myEle = document.getElementById(properties.target_id);
if (myEle) {
    var trgid = '#' + properties.target_id;
} else {
    var trgid = null;
    console.log("Toasty ERROR!: Target ID specified does not exist");
};

And it being using to show the toast notification like this

iziToast.show({
    target: trgid,
});
39

This works,

var id = 26; 
iziToast.show({target: '[id="' + id.toString() + '"]'});

and this does too,

var id = "abc"; 
iziToast.show({target: '[id="' + id.toString() + '"]'});

so you could defiantly,

var id = properties.target_id;
iziToast.show({target: '[id="' + id.toString() + '"]'});
  • if your plugin is asking for #, remove this as it is not used with this method.
40

Works great:

Only thing that happens is that even though the z-index is 9999 it still hides behind the other cell (you cant see it here because the text is shorter) and there is a vertical offset that canā€™t be controlled in the plugin settings.

Looks great, works great :smiley: