GaryLearnTech

Isn’t it the Affinity ID that you use - which is the email address you used to log in to the Serif Store to make the purchase? And that probably doesn’t have the pesky ampersand in it… Of course, a business account purchase might be slightly different.

Only if you’re really short on space (in which case you’ve got bigger problems to deal with). I did the installs earlier this afternoon. The install from each downloaded Serif Store DMG files is simply a drag’n’drop to your Applications folder type of install. It couldn’t be easier!

Looking at the in-app help page for "Location panel (Develop Persona only)" on my Mac version, I see that it has this note at the bottom of the page: "To use the Locate option, you must allow Maps.app to find your location. This can be managed in System Preferences > Security & Privacy > Privacy > Location Services." That makes some sense. I wonder if you have the Windows equivalent disabled on your own machine and perhaps that's why the option isn't showing up?

I haven't got Windows 11 and haven't installed this under Windows 10 yet - I'm working on macOS. (Haven't bothered with iOS yet either.) I'd be very surprised if this didn't work exactly the same under either version of Windows. Out of curiosity, I temporarily set Photo to open in German (which I'm afraid I do not speak, sorry) and - from the Develop persona - this is the option that's required:

Curious! I wonder if there are limitations on the type of files that support this? My test image was a recent snap taken with my iPhone 12 (iOS 16) in HEIC format. Apple ProRAW was not turned on. Or perhaps the default location for German versions is different? It might be worth while checking each of the other panel groups in case it has ended up elsewhere. Here's where it appeared for me by default and why I suggested it: I'm not sure I can add anything more…

You need to be in Photo's Develop persona. Then, if it's hidden, go to Window > Location to enable the panel. Initially, it's likely to be at the top of the Right Studio, in the same group as the Histogram panel.

Hi @All Media Lab - you're missing something subtle in @v_kyr's posts. There are (at least) three different Library folders in different locations on any machine running macOS. 1. /System/Library The central one is located in the System folder and is pretty much exclusively reserved for use by the operating system, so I'll say nothing more about it here. If you're curious, look but don't touch! 2. /Library This central one is commonly used by apps to store global preferences, support files and various other resources. This is available to all users with a login on your computer and provides a central location for commonly accessed settings - one copy that can be read (and sometimes written to) by any user. The / character at the beginning of each of those paths indicates that you start at the top level of "Macintosh HD" and click down from there. That's commonly referred to as the root of your file system. 3. However, over and above those two central Library folders, every user with a login on any Mac has their own user Library folder too, located in the Users folder. That allows each user to have their own individual preferences for how an app is configured, their own individual set of installed fonts and so on. Written out longhand, an individual user's library folder path might look like this /Users/gary/Library You can read that as saying from double-clicking on your Macintosh HD icon (ie, the root of your drive), then double-click the Users folder, then double-click the gary folder and then locate the Library folder within that. Because this is a standard structure, the /Users/yourname part is commonly replaced with the tilde character and your home directory would simply be written as ~/. Taking that one step further, we get the path to anyone's 'personal' Library folder as: ~/Library - - - - So - there are two similar but very different Library paths available: /Library/ ~/Library/ Many of the same sub-folders can be found in both Libraries, so that can be confusing if you take a wrong turning. For example, you're likely to have each of the following folders in both locations: Application Support, Caches, Fonts, Screen Savers - and many others. Now, armed with this distinction, if you look back at v_kyr's posts, you'll see the ~ prefixxing each path, so it's the personal Library that's indicated there. However, your screenshot shows the path at the bottom of the window as the central /Library folder - the one located at the root of your Macintosh HD. And that's why you couldn't find what you were after - you were in the wrong Library folder… Hope this helps?

Sorry for not following up sooner, @vwatson - it's been a busy week. Hopefully you were inspired to experiment with paragraph numbering and are now an expert 😁, but just in case you remained confused, here's a quick video that demonstrates the steps. There's no audio and it rattles along fairly fast, so you may want to replay bits until you can see how the steps work. Hope this helps! TOC demo 2.mp4

I've just tested a way that does work for the style of titling illustrated by @J-Philippe: a chapter number and a separate chapter title. If that's the same for you, @vwatson, read on. Continue to manage your chapter numbers and chapter titles on their own paragraphs/lines with two separate styles. That will give you your full control over positioning at the start of each chapter. Create your ToC using just the chapter title. We'll discard the chapter number and automatically recreate it. In the ToC style for your chapter titles, use the Bullets and Numbering attributes to provide new numbering as part of each title's entry. I used an old text selected more or less at random from Project Gutenberg and did a basic layout. The attached file illustrates the three steps. (I'm hoping that you're reasonably familiar with paragraph styles and, in particular, the Bullets and Numbering attributes.) Look specifically at the ToC style ("TOC 1: Chapter Title") highlighted below. Once you've got the numbering recreated, the trick is to use the "Text" field to add "Chapter" back in to the auto-numbering. See the second screenshot. (NB I also had to add an extra tab stop to that style. If I had just used a space character between the chapter number and the title, that wouldn't have been required.) It looks a little convoluted at first, but it's actually really easy. Hope this helps! compound ToC.afpub

No, locking the file would be optional. I never thought about opening the file from within Photo (File > Open…) - but originally I had the impression that @ThatMe was opening the template files from the Finder, so this was an alternative for that style of workflow.

Hi @ThatMe There is a way of extending Paul's suggestion that's available for Mac users, by using an old Finder 'trick", instead of producing an Affinity template file. Save your document to a suitable location as an ordinary .afphoto file locate your file in the Finder single-click it, to select it File > Get Info Click the "Stationary pad" checkbox, shown below close the Info window What happens once you've done this is that when you double-click your template file, macOS immediately makes a duplicate file for you and opens that instead. In this case, it would produce a file called "template 01 copy" in the same location as the template itself. You'd presumably want to rename the new file pretty quickly and probably save it to a different location, but it does have the advantage that the file remains a .afphoto file, so should always open straight into Affinity Photo. It's probably not perfect solution, but might be worth spending a little time experimenting with - perhaps it could fit your workflow? Stationary pad files can be reverted to ordinary documents by unclicking the "Stationary pad" checkbox. https://support.apple.com/en-gb/guide/mac-help/mchlp1341/mac

Hello @hector.as92 - welcome to the forums! Ajusting the Phase value in the Stroke panel should allow you to balance the dashes. (¡Bienvenido a los foros! Ajustar el valor de Fase en el panel Trazo debería permitirle equilibrar los guiones.)

If you're not already doing it and just hadn’t commented, consider adding the margins (and any other guides you might want to use) to the same master page that has your page number. Then fitting brand new text frames - or flowed text frames - should be much easier since your margins will be present and consistent on every page. Hope this makes sense?

Hi @BlueSailing I've had a tinker with this and I think I can put my finger on two problems that are bothering you. First of all, I can bring both pages in (right click on a page in the Pages panel and select Add Pages from File… That seems to work fine. It's only when I try to change the text flow between the frames that things really get messed up. But that was easy to bring back under control. Using the text tool, click inside what was the first paragraph of one of the pages. Then in in the Flow section of the Paragraph panel, set the menu beside Start: to On Next Page (as shown below). That's a manual override that will put that paragraph at the top of the next page and restore the layout you had in the single page files. Don't use a series of carriage returns (the enter key) to do this. The other thing I spotted that I would do differently is how you're configuring the Float settings for each pinned image. Looking at your earlier pages, you seem to be left and right aligning the photos on or close to the text frame margins (a mall offset on the right for the drop shadow?). But you're floating/anchoring the images to the character to which they're pinned. I would align to the columns, as shown below right. This way, you can edit the text later on if required and not worry about your pinned images moving. The screenshots below are from the Harry King image. If you don't want the images flush on the margin, you could offset it slightly. For the image of the Anita, you'd select Inside Right of Column. Note that when you change the pinning rule, Publisher maintains the old position (ie it updates the Offset value), so you'd manually have to set the offset to zero (or whatever offset). Hopefully that will help you make some progress? (NB I haven't seen "this topic from a week ago", so I don't know if anything I've said here repeats any of that post - or even contradicts any of it.)

Are you using a really old version of Word? How are you trying to 'open' your PDFs? I've opened (File > Open) PDF's from various sources straight into Word on a number of occasions over the years. Right-clicking a PDF on my desktop and selecting Open With > Microsoft Word also works. I'm using Word 365. At work, I've had Windows-using colleagues open complex PDF's straight into Word 2019 and possibly some older ones using Word 2016 in times gone by. The results have been a little mixed but have usually sufficed. In a couple of quick test documents produced just now out of Publisher, I selected the "PDF (digital - high quality)" export preset. I wonder if some of the other presets my not work so well (or better!)?

Hi @Ria - don't depend just on the File > Open Recent option. In the Finder, start by opening your Home directory. Select File > Find (or press cmd-F). Type ".afpub" into the search field that you should see in the top right corner (unless you have customised your Finder windows). After a moment or two, depending on the performance of your machine, you should get a list of all the Affinity Publisher files saved within your home directory. If you might have saved them outside your home directory, select "This Mac", as shown below left, to broaden the search scope. You will have several date columns available. Choose whatever seems most useful and sort in descending order to show most recent files at the top. Hopefully, you'll be able to locate your missing project. (Various refinements to that search could be made - you could for example, combine various search criteria at once - but that should get you started.)

I came across this a couple of weeks back and had been planning to log it at some point. The preview has the bug, but fortunately when Generated, the vertical alignment is sorted.

Perhaps @CrashX was referring to the New Document preset, simply called "Business Card"? It appears near the end of both the Print and the Press Ready groups so, depending on how large you've set the New Documents window, you may have to scroll a bit to see it.

I just took a quick look at my own list of rules from Little Snitch. I have whitelisted these domains for each of the three apps at some point: serif.com seriflabs.com serifservices.com s3.amazonaws.com (@R C-R I do have a vague memory that one of them was definitely for the splash screen, though I don't now remember which one.) I've also got these isolated ones. Pixabay is pretty obvious… I'm not sure what triggered the final amazonaws domain.access or how often it has been used since. Affinity Photo: pixabay.com Affinity Publisher: s3-eu-west-1.amazonaws.com Hope this helps!

Hi @debraspicher I wonder - could this be caused by a side effect of a browser extension or plugin? If/when you encounter this again, perhaps you could try to "Diagnose Firefox issues using Troubleshoot Mode": https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode If that does appear to resolve the problem, you'd need to return to Firefox's normal mode (just restart Firefox) and try working through the active extensions, disabling a few at a time, to try to identify the specific culprit(s).

The small images I was getting initially were 320x240 - and seemed to be a standard preview size provided by Blogger. Actually, looking back, I see some were 640x480 too, good for previews but still pretty small. When pasted onto a Publisher document (I was initially using Safari) they appeared small - postage stamp sized. I expect they would be small if pasted directly into Word too. This was when copying individual images, one at a time. Whereas in my all-at-once Word test, the larger images came through and typically filled the page width with no apparent loss of quality - no fuzziness due to scaling a tiny image too large. So that's the simple basis on which I’d judge the is-this-the-small-version-or-the-large-version question.

Hi @PM31 and welcome to the forums. a) I wonder if your missing images are somehow coming in with an offset? Try zooming waaaay out and see if you can spot your image. Clicking the image in the Layers panel first may assist. In fact, try checking the Transform panel for a large X or Y offset. If that locates it for you, either just drag it back into the page or set the errant X or Y value to 0 initially and then fine-tune as normal. If that doesn't help, I think a screenshot of your full screen is going to be required get to the bottom of this missing image problem. Before taking the screenshot, make sure you've clicked on the image in the layers panel so that we can try to glean as much info as possible. b) I don't think that you're going to be able to get the text and graphics in one pass. At least, not with that link you shared. Even if you could, it would be the low-resolution versions of each graphic that you'd get. Looking at the first image on your page, if I right click and copy it, the image in my clipboard is 320x240px - the low-res preview version that readers get initially. If I right-click the image and select Open In New Window, I get the full 1600x1200 image. Alternatively, if I single click the image and go into Blogger's image gallery view for the page, I can get the high-res version. I'm not familiar with the editor screen for Blogger, but I wonder if stepping back into the view and copying it all from there might not work better? c) Failing that, in my testing on my Mac, copying the text and pasting into Word brought through both the text and the full sized images. (I've got Word 365, though I suspect this would also work with older versions.) Save the Word document as a file and then use File > Place to get that file into your Publisher document. Hope this helps?

Hi @Xanthe G - welcome to the forums! Indeed it has! I've recently (just about) finished updating an old design for use in Publisher and have shared it with the first of the colleagues in my team by saving it as a template and passing that file to her. You'll find information about document templates here: https://affinity.help/publisher/English.lproj/index.html?page=pages/GetStarted/templates.html?title=Document templates Hope this helps!

Hi @ChrisA380 I don't actually use this feature myself, so I can't be 100% certain, sorry. But I reckon that anything you enter will be retained if you save and send your image as a native Affinity Photo file - ie File > Save, to produce a foo.afphoto file. However, if you're exporting as, say, a jpeg file, check the "Metadata in exported images" section of the Metadata manual page. There appears to be one or two exceptions. https://affinity.help/photo/English.lproj/index.html?page=pages/Panels/metadataPanel.html?title=Metadata panel Once you've read over that page and are feeling more comfortable with the feature, set up a trial with a sympathetic friend or colleague and ask them to check what they can see when you send them a test file. (It's been a long time since I was seriously into photography - especially with traditional cameras, not 'just' smartphones - but I do recall my last version of Photoshop (v3? can't remember now) had a very similar set of metadata fields.) Hope this helps!

Hi @ChrisA380 It looks like you want to use the Metadata studio panel. If not already visible, select View > Studio > Metadata. Click the pop-up menu at the top left, currently showing EXIF info, to see other data groups that you can enter manually. Don't overlook it - there's also a standard Studio menu control at the top right that offers further options. I've cheated a little with the screenshot below to illustrate both sides at once.