Thanks. The one I needed to change was actually archive-page-with-sidebar.php. but I have changed both.
Thanks
Thanks.
Could I change ‘Newest Items’ title for alternative text? where do I do this?
Excellent, many thanks. Could you tell me which file controls these amendments so I can keep a back up?
The updated release brought back the link on the breadcrumbs. could we remove it again as done by Shahriar over tread ‘remove breadcrumb links’. ‘home’ breadcrumb still gone -which is good.
thanks
Thanks. Is it possible to reduce list on newest items to show 10 packages max only?
Thanks. I see it now loads all packages. It would be nicer to have pagination thought.
On the ‘NEWEST ITEMS’ landing page which I didn’t have before. It really doesn’t work. I have too many items, the item at the top of the list is an old packaged, the ‘newest’ at the very bottom (out of 20 -too many) is not really the very newest published on this job. So all together this page is a bit of a puzle!
Can I not have this new landing page? Alternatively, have it, but loading no more than 5 items, newest on top. FYI, the latest package that should load on this job in test11 which doesn’t load on the list, so I don’t get it!
Many thanks
NOT QUITE SO. Main admin user has more than 20 packages under ‘habitar’ tab but not all are loading. See screenshot. I have also tried changing items_per_page=”10″, thus I would have expected to see pagination? but neither is happening.
I have now reset pagination to 5 on this page. So you cant test logged in as ‘tempad’ -which still has 11 packages allocated under this category.
I have applied the latest update to DM and it seems it removed some of the customisation. I had a backup of the amended file to 09/01/2017 but the ‘home’ breadcrumb has come back and despite overwriting the file on server with my backup, the ‘home’ still shows. Could you re-apply customisation to delete it?
yes, but that doesn’t tell me the last digit and I thought there was an update available for 4.6.2 (or so) which now is not showing any more, and I do not know why. Did you applied?
Did you applied the update that was still available? The alert is not longer showing. How do I check which version I’m running?
Ok. But I am a bit confused. I have changed the names for each of be different. As noted packages load correctly, but one has to click on ‘tab1’ all the time to see the packages loaded under ‘tab2’. Can this be fixed?
Good thanks. anything you changed?
Well not quite, they are named the same but in fact they are different. Each IDs is different ie Tab1/Habitar is 201 and Tab2/Habitar is 203
But I have set ‘skip package’ on PDF stamper. ?
Yes, you are right. just created a new package by ‘add new’ and it worked.
So why this http://www.habitararchitects.co.uk/download/test-without-emcryption-new-package-not-working/
still doesn’t!?
Action please!
I am unable to download newly created packages. It seems older than a week or so work ok, but not the newer ones. If I create a new package by cloning an old one it works ok, but new ones via ‘add new’ do not.
Not sure it is related but I applied a theme update a week or so ago
Not quite the same as I though. Old packages downloading correctly. HOWEVER newly created ones DONT!
HELP ASAP please!
Thank you!
AND, just got this back from server host, So please could you dealt with it ASAP. thaks
The PHP www-error.log displays a PHP Fatal error which likely correlates to each time you attempt a download. You can test this yourself by attempting the download, then checking the log, and looking at the timestamp of the error message, or just looking for a new entry at the bottom.
The error message mentions the plugin ‘download-manager’ specifically, so this is likely the cause of the failed downloads :
[19-Jan-2017 23:20:43 UTC] PHP Fatal error: Call to undefined function WPDM\wpdm_is_url() in /srv/data/web/vhosts/www.habitararchitects.co.uk/htdocs/wp-content/plugins/download-manager/libs/class.FileSystem.php on line 30
This is an error with the plugins code, it is calling a function that is not defined within the code. I suggest you pass along this error to your plugin developer.