Hi Dirk,
I suspect that the declaration of arrResponse might be the problem. Looks like it’s a single byte. Try making it a small array, similar to how you declare arrBuffer.
Hope that works!
-Loren
↧
Server error when uploading images (PF 2016)
↧
Suitcase Fusion 7 and CC 2018
Terrible move extensis - as you can see your loyal, professional customer base are already seeking alternatives.
I am in the same position of having been fleeced by your cash grab mentality. I was forced to upgrade to SF7 from in under 6 months due to Adobe rollouts - not your control, thats fine I get it. But then I upgrade to SF7 and again, 8 months in and voila, upgrade again! And surprise! No column view!
Your software is no longer a flat rate fee, it’s now, on average, a yearly fee.
It used to be normal to provide updates to software, even prior versions - get it together and have some respect for your clients.
↧
↧
Suitcase Fusion 7 and CC 2018
The fact is that Suitcase 7 works fine with CC2018 as long as you don’t need the auto activation. Frankly there is nothing that great in CC2018, but it is hard not to update, and of course that means you need to get a new Suitcase too.
Extensis has been obsoleting SC since 5 by refusing to provide updated activation plug-ins for later versions of CC.Now I don’t mind paying a few bucks for an updated version, and the last few have been fine, but the UI overhaul this time is incredibly inefficient for folks with lots of fonts, like any professional user. I have left 7 on many of our seats and we’ve just lived with the inconvenience of opening fonts manually as needed.
↧
Server error when uploading images (PF 2016)
Dear Loren,
nope, that can’t bei the problem. The declaration you’ve mentioned IS an array declaration (it’s a dynamic array without fix array limits), and actually the program never reaches that point. Before we run into the timeout since PF isn’t completing the http request (see log file).
The problem really must be located on PF side.
Best
Dirk
SOLVATEC
create software_webdesign_arts
Deutschländer, Lock und Wurdack GbR
Storkower Str. 113
10407tel:10407 Berlin
---- Loren Barr schrieb ----
[https://avatars.discourse.org/v2/letter/l/cc9497/45.png] Loren_Barrhttps://forums.extensis.com/u/loren_barr
December 4
Hi Dirk,
Sorry you’re having trouble uploading with the API. We’ll get it all sorted out.
Can you tell us a couple things:
• What version of Portfolio Server are you working with?
• Can you send us your code that does the upload?
• Does the uploaded asset show up in the catalog after you’re done with the upload?
• Does your code get a response code from the server? If so, what is it?
Thanks in advance,
-Loren
↧
Suitcase Fusion 8 – Features Request
Here is a different feature request (YES! to all of the above tho) I wish there was a more sophisticated way to preview fonts than QuickType. At least add tracking to see how letterforms combine (FontExplorerX allows this, along with almost all the browser based samplers on font company websites)
If I could have my wish, it would be a floating window where we could craft a few words or short sentence with line breaks, control of leading and tracking, color and maybe even the ability to adjust the justification and then use the column view to select fonts interactively, watching the preview windows change as you mouse over the font in the column view. You could do real type searches in a window like that.
I often activate hundreds (thousands!) of fonts at a time and use the interactive font menu in Illustrator to do the exact thing. But why not have it be a part of Suitcase?
↧
↧
Is every year another $60?
I would be happy to pay for upgraded auto activation plug-ins….
↧
Server error when uploading images (PF 2016)
Hi Dirk,
It looks like you’re running into something like this: https://developer.jboss.org/thread/269615. We are using a similar version of jboss.
Here is a reference java implementation of the upload: http://doc.extensis.com/api/portfolio-server/HTTPuploadFile.html
In particular, note the headers that are sent under the comment “Set up the connection URL.”
My guess is that you will need to specify the Content-Length header.
-Brooks
↧
Server error when uploading images (PF 2016)
Also, are you able to upload files using the classic Portfolio client? (This is at host:8090/classic for Portfolio v3.x and at host:8090 for prior versions.) The classic client uses the FileTransferServlet which appears to be what you are using.
↧
Server error when uploading images (PF 2016)
Dear Brooks,
thanks for your quick answer. Regarding your hint to the content length: The webclient class which I’m using is offering a “UploadData” method. When using this method, the content length will be set automatically depending on the submitted content. I have another implementation where I’m using a http_request-class. Here I have to set the content length (which I do) – but with exactly the same result at the PF side.
But I read your mail as if there’s another method instead of the FileTransferServlet to upload files to PF via the API. Is this the case? I can’t find any other in the documentation…
Best,
Dirk
↧
↧
Is every year another $60?
Sweet! Need my Paypal account?
↧
Batch Process Zipping files
Is there anyway not to have Download or Batch Process Zip files? All it does is make extra steps for users to have to unzip files to do anything with them. There should at least be some option to Zip/Not Zip files when Downloading or Batch processing.
↧
Server error when uploading images (PF 2016)
Can you verify that you can upload files to Portfolio in the classic (flash) client? Also, can you please tell me what version of Portfolio server you are using?
↧
Suitcase Fusion plug-in slows Adobe InDesign to a crawl
When the Suitcase Fusion auto-activation plug-in is active, any change made to an Adobe InDesign document results in the “spinning beach ball” with a lag of about 15-20 seconds. This problem exists in both Suitcase Fusion 7 and 8, and Adobe InDesign 2017 and 2018, and is not document-sensitive.
↧
↧
Upload an asset VIA the API
Hi Brooks,
I have found the issue.
When portfolio was first set up some fields were set to required.
Because I wasn’t providing these fields then I got a 400 response.
I removed the required fields and it now works.
Thank you for your help regarding this.
Michael.
↧
Suitcase fusion 8 is a desaster in font management!
Dear Suitcase Team,
we have been big fans and users of your font management for years. Basically, since the ATM faded away.
But Suitcase 8 is unfortunately a disaster, even if it tries to be visually very clear and concise. Unfortunately, this counteracts all previous workflows that have been painstakingly built up over the years. And there are not even customization options for the interface for “Pro” users.
Merging the preview and list display into a hybrid view is not a good substitute for one or the other. On the contrary: It cuts the program sensitively and you don’t even know what you are actually using Suitcase for? Basically, only to auto-activation, which is pretty little as a feature.
It’s not exactly true that Suitcase has been THE perfect program in the last few years - there were a lot of gaps. Be it the annual mandatory update due to the Adobe plugins, the missing support for quasi-standards like Sketch, the strangely different interface of Suitcase itself, which doesn’t feel really modern and up-to-date, etc…
We wonder what kind of problem the Suitcase programmers wanted to tackle with this huge change? After all, only countless new problems have been created… which is surprising to us, because it seems that you don’t know your customers very well, Otherwise there would be at least the option to adapt the interface via options?
Will there be any changes to the interface in the next few weeks – or shall we make the transition the Font Explorer?
Greetings,
Matthias
↧
Open letter to anyone listening at Extensis
I sent this message to Clint Daeuble, the Product Owner of Suitcase on the forums two weeks ago but got no acknowledgement or response. So I emailed it to ea_suitcase@extensis.com as instructed elsewhere. That was over a week ago and that email, too, has been ignored.
Companies usually only stay quiet like this when they’re trying to weasel out of a problem, or hoping that people will forget and it will go away. I sincerely hope that is not the case here.
I’m registered for the Suitcase webcast on Monday and am hoping to get some kind of answer during the promised Q&A session at the end.
Hello Clint,
It’s about a month now since I and others have been giving feedback in the Features Request thread as you asked us to, and we’ve not heard anything. Can you please update your customers on what is happening with the application and the missing features?
I read the “solution” that was posted. I don’t mean to be rude - although I do need to be blunt - when I tell you that is an absurd answer to the problems I and many others are experiencing, and is in no way any kind of solution.
I would assume that the Suitcase developers thought carefully about the changes, and would therefore be able to provide a strong justification for them, as well as a clear explanation of how the changes have made their users’ jobs easier? Where is this information? Where is the compelling description of how our workflow has been improved? The product page at extensis.com is suspiciously light on details, and consists mostly of marketing-speak telling me this new release will “focus on core font management tasks” without expanding on what that means, or indeed what Extensis thinks those core font management tasks are. Nevertheless, I’m informed I will “Rediscover the Joy in [My] Font Collection”.
How?
I already spent some time (here) detailing the shortcomings as I see them, and offering my ideas on how to deal with them. No-one at Extensis has even acknowledged them, or anyone else’s so far, let alone actually address any of the things people are saying.
By all accounts, many of these problems were highlighted during the Suitcase Fusion 8 beta phase, but it got released anyway. It is worrisome that Extensis does not seem to understand the way that many of their users actually use the software.
I urge you to demonstrate that you understand your users’ problems and that you have solutions in the works that will adequately solve those problems.
thanks for listening
Ian
↧
[solved] Postscript name does not match display name in Suitcase Fusion
So, I have this same problem - but maybe on a larger scale
I have nuuuuumerous fonts with the same identical name, but clearly they are a set of bold,italic,light,condensed, etc.
And, you can see top right in my screenshot, the postscript name is still there, hiding.
How can I restore the display name to the postscript name?
…this thread is marked solved, but I think that’s a bit misleading as mhulse chose to avoid the real problem by deleting the “duplicate”.
Thanks!
↧
↧
Upload an asset VIA the API
Glad you found the problem! Funny, I thought I tested that, but that I got a different error. Maybe different version of Portfolio server?
↧
Open letter to anyone listening at Extensis
I’m with Ian, 100%.
Please respond to your customers concerns, Extensis.
↧
Renaming Fonts: Is it possible to restore to Postscript name?
I’m reposting this question in a new thread, because the previous one was marked solved, but if you read through the solution, it’s clearly not.
Can the postscript name of a font be used to restore the display name of a font? I don’t see any way to do this inside of Suitcase Fusion (7), but potentially using Font Doctor?
Here’s the problem, using the font Akzidenz Grotesque;
I have 3 versions of the family of this font. They are similar but different.
The preview window shows I have regular, bold, heavy, light, condensed, expanded, etc, but the display name (in column view and preview) shows ALL of them as “Akzidenz Grotesque Regular”.
If I select an individual font, say the Bold one, the info column on the right side shows the postscript name AkzidenzGrotBold.
So the fonts full and correct name is there - yet the display name shows regular.
↧