Avatar for Username

חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

אשכול זה הועבר לארכיון. נא לשאול שאלה חדשה אם יש לך צורך בעזרה.

When is Firefox going to resolve the problem with Tailwind concerning not being able to schedule pins that have Pinterest as the source?

  • 1 תגובה
  • 1 has this problem
  • 1 view
  • תגובה אחרונה מאת WestEnd

KarenJR
KarenJR
more options

I'm an affiliate marketer who uses Tailwind to schedule my pins on Pinterest. If a pin has Pinterest as it's source, it is rejected and won't schedule. This is what Mollie from Tailwind told me the reason was:

It seems like Firefox is giving us some trouble due to some changes recently made by Pinterest :( Our development team is aware of this issue, and we'll be sure to let you know as soon as it's updated and Apple approved the update! In the meantime, we highly recommend using Chrome as all seems to be working well on that browser!

I don't want to use Chrome, so I'm eagerly waiting for Firefox to please fix this. In the meantime, this has greatly affected my marketing in a negative way.

I'm an affiliate marketer who uses Tailwind to schedule my pins on Pinterest. If a pin has Pinterest as it's source, it is rejected and won't schedule. This is what Mollie from Tailwind told me the reason was: It seems like Firefox is giving us some trouble due to some changes recently made by Pinterest :( Our development team is aware of this issue, and we'll be sure to let you know as soon as it's updated and Apple approved the update! In the meantime, we highly recommend using Chrome as all seems to be working well on that browser! I don't want to use Chrome, so I'm eagerly waiting for Firefox to please fix this. In the meantime, this has greatly affected my marketing in a negative way.

כל התגובות (1)

WestEnd
WestEnd
more options

Screen shot of the error? What changes did Pinterest do? Apple isn't a Browser. If you want the Mozilla team to know more you should do a bugzilla report so they get it faster and verify the problem.