Blog2

SEO is available for Public (B2C) storefronts only.

What SEO fields are available?

You can add SEO data in multiple areas, so to keep it simple, I will list them all.

1. Product category home page. When you are viewing this page in Admin you will see the ‘Edit Category’ button at the top. This opens a popup where you can add the SEO info for this page.

2. For each subsequent category you add, you will see the SEO details when you either create or edit that Category.

3. Adding SEO to a product. This is not so straightforward because a product can appear in multiple places so the process is slightly different. Why? because we allow you to have the option to change the SEO for each page the same product appears. You will find the SEO settings in the box called Categories when you edit a product.

When a universal Product or Category exists in your Public Storefront you can add SEO settings by clicking on ‘More’ when you hover over the tile.

Loading data into templates.

When a customer clicks on an editable product, you might want their data to load into the template automatically. This makes things faster and simpler for the customer and can cut down on mistakes.

Loading from the database.

• Use a dataloader at the top of the templates list of objects (on the Admin side)
• Based on who the user is, you can load their user data, their department data or their departments default address
• You can also allow them to select someone else in their department

More about dataloaders here..

Loading from Hashtags

• a Hashtag is unrelated to orthodox database (users, departments etc)
• If you nominate a hashtag (simply creating a new one like ‘Airport’) whatever the user writes in, will be stored on that hashtag.
• Any field with the same hashtag will automatically load the same data.
• There are two modes – hashtags saved per user and hashtags saved per storefront
• Per user means that whatever John writes for a field will not be shown to Susan.
• Per storefront means that when John writes something in, that becomes the new content for the hashtag, until the next user changes it.

Example 1 = User based = The first time John sees this field and can edit this field, on any product, the Airport hashtag will be empty. He can fill in ‘JFK’. Any other field on that product, on any page will then also load ‘JFK’.

The second time John sees this field, it will show ‘JFK’ automatically. In fact it will always show JFK until John changes it.

Because this is a User based hashtag, when Susan sees the field for the first time, she will see it as empty, and can write in ‘Paris CDG’.

Example 2 = Storefront based = The first time anyone in the Storefront sees this field it will be empty. John or Susan can write ‘Sydney’. For all users, all subsequent fields with the same hashtag will have ‘Sydney’ in them. UNTIL someone, anyone, changes it to ‘Madrid’.

Want to be 100% sure your emails are being delivered?

You can now choose to have all the system emails sent via a 3rd party. This could either be your own email provider, your company email server or a 3rd party Transaction email provider like Mailchimp, SparkPost or SendGrid

Setting this up is easy in PrintJob. All you need to do is enter the following details provided by your mail providers.

There are some things to remember. If you use a 3rd Party you will need to authenticate the domain of the email you wish to use as a sender. This email will then need to be added in PrintJob.

Some of these 3rd party providers share their users on the same IP address and any SPAM can result in the IP being blacklisted which means some emails will not go through. So you should consider asking for a unique IP address to make sure no one can use the IP to send their SPAM

The following doc is intended to list working practices at PrintJob and as such, will be constantly reviewed and updated.

Future Development on Security

There is always pressure to increase security.

PJ is currently debating whether to increase the password requirement so that they include one uppercase letter, one special character and alphanumeric characters. However, we’re very keen not to impact usability and we are aware of the fact that we aren’t a bank.

We could also allow Google or Microsoft logins.

Are you a target? Threats?

Does PrintJob vet its staff?

Yes. Everyone who works at PrintJob is properly checked, to ensure that do not themselves pose a threat to data security.

How does anyone get Support?

PrintJob Clients (Admins) can communicate directly with PrintJob Support via an in-app communication tool. Help articles are also found on https://printjob.com/support/

Who can see my Support Queries?

Only PrintJob staff.

What happens when the Systems go down?

Our Terms and Conditions page explains this. Downtime does happen, but when it occurs in UK office hours, it has never lasted longer than 3 or 4 hours but is more often less than 20 mins. Worst case scenario (in the event that the data is unrecoverable) PJ can restore from backups within an hour or so.

Cloud Server Specs

4 core CPUs, 8GB of RAM, 1000GB of RAID storage and 5000GB of monthly bandwidth on all servers. Further upgrades are possible.

On Brexit

We’re waiting to hear what impact Brexit will have on UK businesses and the EU. Aside from our programmers, we don’t maintain any presence in the UK. We’re based in France and Germany. We do have potential plans to move our company to the Republic of Ireland if Brexit causes any issues.

See also

Linode
ISO
GDPR
PrintJobs Response to GDPR
PrintJobs Terms and Conditions
PrintJobs Privacy Policy

You can see the list of fonts available in your system in System Settings > Fonts

To upload new fonts, you need to a) have a suitable license to use the font and b) make sure its properties allow it to be ’embeddable’. You can upload any windows font, or TTF, OTF, or Postscript Fonts. The postscript fonts will require 2 files to be uploaded, usually a PFM and an AFM.

Please note any system fonts you find in the system are there for demonstration use only. They will NOT be embedded into any pdfs.

If you are using Data Sets in your editable templates, you can now allow Data Sets manipulation through our API.
You can retrieve, update, create and delete any Data Set or any of its elements, called Data Points.

What are datasets?

DataSets are used in Editable Product templates. They are used to group sets of values (DataPoints) for selection by users during the ordering process. Each DataSet belongs to a specific company and can have one or more DataPoints which users can select from a dropdown when they fill in the template fields. Each DataPoint contains up to 9 separate columns that can store strings that would appear in the final product.

Retrieving data from API is relatively easy. All you have to do is to navigate to the desired endpoint and you get a list of all objects currently present in the system.

Request:

curl "https://api-domain.printjob.com/v2/dataSets" -u "sk_test_key":

Response:

{
  "object": "list",
  "count": 2,
  "data": [
    {
      "object": "data_set",
      "attributes": {
        "company": "company_YEkjyNa0q6GXMlR83Bm9",
        "name": "Office Addresses"
    },
    "id": "data_set_8lwpXy6JRgdDLYmBaKO9",
    "test_environment": true
    },
    {...}
  ],
  "links": []
}

Once you get your list you may want to update one or more of the objects. This is where new functionality comes in. PrintJob API is built around RESTful approach, so to affect a change in the contents of the object you will need to switch to a ‘PUT’ verb in your HTTP request.

Let us assume that first object from the truncated list above is the one that interests us. We want to change its name to ‘Company Addresses’. Let us try that.

Request:

curl -X PUT -d "attributes[company]=company_YEkjyNa0q6GXMlR83Bm9&attributes[name]=Company Addresses" "https://api-domain.printjob.com/v2/dataSets/data_set_8lwpXy6JRgdDLYmBaKO9" -u "sk_test_key":

Response:

{
  "object": "data_set",
  "attributes": {
    "company": "company_YEkjyNa0q6GXMlR83Bm9",
    "name": "Company Addresses"
  },
  "id": "data_set_8lwpXy6JRgdDLYmBaKO9",
  "test_environment": true
}

Let’s walk through the example above.

-X PUT flag sets our request verb to PUT, which tells API that we want to modify an existing record
-d “…” contains a list of all attributes of the model with the values we chose to change.
NOTE: Remember that you need to send an entire object, with all of its attributes you don’t want to change prefilled with current values as any missing attributes will be set to empty.
URL part contains an URL to dataSets endpoint and an ID of an object we want to modify (data_set_8lwpXy6JRgdDLYmBaKO9 in this case)
-u is the authentication part where username is (the part before the colon) is your API key, and password (the part after the colon) is empty.

Request returns an updated object which you can immediately use, modify again or even delete. As you can see it’s ID remained the same while values of desired attributes have changed.

If you would like to add a new DataSet then you need to use POST verb and send the data in a very same way as in case of the PUT request.  Check out the example below:

Request:

curl -X POST -d "attributes[company]=company_YEkjyNa0q6GXMlR83Bm9&attributes[name]=Home Addresses" "https://api-domain.printjob.com/v2/dataSets" -u "sk_test_key":

Response:

{
  "object": "data_set",
  "attributes": {
    "company": "company_YEkjyNa0q6GXMlR83Bm9",
    "name": "Company Addresses"
  },
  "id": "data_set_q21ZlAJGR27Dzd6Pxpnr",
  "test_environment": true
}

Please notice the differences from the previous example.
In the request, we do not supply the object ID as it does not yet exist. We send our data directly to DataSet endpoint and let it do its magic. The ID of a newly created DataSet will be included in the response.

In the case of the DataSet, there are two attributes – company and name. Company is a reference to a company present in your system and takes the form of that company’s ID. Name is just a string that will describe the DataSet. Both are required, and if you omitted any of them your request would fail and return an error describing the problem. Please refer to the documentation to see all the required attributes of objects you are working with.

If you then wanted to remove one of your DataSets you could use DELETE verb in your request. Example follows:

Request:

curl -X DELETE "https://api-domain.printjob.com/v2/dataSets/data_set_q21ZlAJGR27Dzd6Pxpnr" -u "sk_test_key":

Response:

{
  "code": 200,
  "message": "Success"
}

As you can see this one is pretty straightforward. All you need is an ID of the DataSet you want to remove and a DELETE verb. Use it with care as removed items can not be restored.

NOTE: Removing DataSet with associated DataPoints will remove those DataPoints as well without any additional checks or questions. Always ensure that you are deleting correct objects and don’t try to guess the IDs of objects to delete!

DataPoints

Each DataSet contains one or (usually) more DataPoints that allow users to choose values they want to appear on their products. To retrieve and manipulate DataPoints we use the same techniques as described for the DataSets above.

Just like with DataSets belonging to a Company, DataPoints belong to a specific DataSet. To create a new DataPoint for our DataSet we would follow a similar path as we did with DataSets.

Request:

curl -X POST -d "attributes[name]=Main Office&attributes[sort_order]=1&attributes[value_1]=10 Some Street&attributes[value_3]=Anytown&attributes[value_4]=AN12YT&attributes[data_set]=data_set_8lwpXy6JRgdDLYmBaKO9" "https://api-domain.printjob.com/v2/dataPoints" -u "sk_test_test":

Response:

{
  "object": "data_point",
  "attributes": {
    "data_set": "data_set_8lwpXy6JRgdDLYmBaKO9",
    "name": "Main Office",
    "sort_order": "1",
    "value_1": "10 Some Street",
    "value_2": "",
    "value_3": "Anytown",
    "value_4": "AN12YT",
    "value_5": "",
    "value_6": "",
    "value_7": "",
    "value_8": "",
    "value_9": ""
  },
  "id": "data_point_wJq6G5l4xR0XzovWNeL1",
  "test_environment": true
}

As you can see, we sent only the attributes we wanted to hold a value. Other attributes were set to empty. DataSet is a required field and needs to hold an ID of an existing DataSet.

Modifying and deleting DataPonts is very similar to DataSets and if in doubt you can consult our documentation for specific examples.

The PJ system is set to respond to ‘Trim Boxes’

Or, more accurately, clients will only see previews of the trim box area and if no trim box then the crop box. If neither have been set then the Media box.

To set the trim box go into Acrobat Pro and choose Tools>Print Production>Set Page Boxes

Heres a video which shows the process

The most important thing to know is that there can only be one SPF record per domain so if you have more than one you need to join them.

Here is what you should do if you are merging 2 SPF records (ie adding PrintJob to Microsoft outlooks SFP)

Change the Host: as outlined in red and add another include:spf also marked in red.

Host: @

TXT Value:  v=spf1 include:spf.protection.outlook.com include:spf-s1.printjob.com ~all

Information about what SPF data needs to be added can be found when you click Authenticate Email. These instructions vary depending on where you are based in the world but overall they look something like this. 

SPF records take time to propagate so be a little patient.

If Host: is giving you trouble you can replace your domain with @ and it should work.