-
Posts
542 -
Joined
-
Last visited
-
Days Won
1
Everything posted by ceberlin
-
In the context of dates, what I really would find useful, is a date for the latest hit. So I could, after a period of time, delete those redirects, which had no hits since that period, so those links don't seem to matter any more. That helps to keep my list short.
-
I see 2015 years ago also, but only on the Mac (localhost dev server using MAMP). On the Linux 2.4 live server the dates are correct.
-
Tonight I restored the database to get JumpLinks back and tried a bit further. To get some traffic on the site, I used a dead link checker with some threats (not to many) to challenge it. Then the trouble started. The problem I got indicated an unnormal behavior like a loop. Too many requests. I found out that it is not the links. I had an entry in the module's Legacy Domain field. Example: http://domain.de/drupal/. There might have been a loop, maybe simply because the new site is https://domain.de only. Or there is some other problem with that field (or a misunderstanding from my side, what it does). Removing that entry (I forgot about that entry this morning - since the field is always collapsed) cured the issue, I think. Site and server are up to speed, regardless of running the link-checker again.
-
I actually had to uninstall the module - it was causing excessive mysql database connections (not usage) and my webserver nearly stalled. Maybe I run into a loop or something? I was redirecting from an old Drupal website to PW and used about 70 simple type redirects, such as sources /drupal/page1/ Got this (on the latest PW dev) Error: Exception: SQLSTATE[HY000]: General error: 1116 Too many tables; MySQL can only use 61 tables in a join (in /wire/core/PageFinder.php line 300) Error: Exception: DB connect error 1203 - User already has more than 'max_user_connections' active connections (in /wire/core/Database.php line 68) I cannot say 100% that this was Jumplinks. I just noted that the performance was back to normal after I uninstalled the module. So this is just for information in case anyone else can confirm this.
-
Nice module, thank you. Interesting to see the old links. If you have a lot of links to remove, it can be a lot of click-click to get rid of them one by one individually. What about checkboxes and only one button?
-
PageTable: srolling and scrolling and scrolling
ceberlin replied to ceberlin's topic in Modules/Plugins
Hi, thanks for the link ...that issue report seems to cover part of my issue (where there is a real bug and not only a concept question). The modal problem seems to have to do with outdated JQ UI code used here, at least that is what I think. -
I use Apple Safari, PW latest dev: I find it tricky at times using the pagetable field. When a modal opens with the "child" page, the modal itself is scrollable and can easily scroll out of view. (The window should not be scrollabe, if the modal is open. I think.) Inside of the modal there is the page which is scollabe and inside of that are CKE fields which are also scrollable. That is not easily manageable, there's not much space then, the CKE menu is out if focus quickly and if I scroll up to fast, Safari shows that bounce effect and scrolls the outer scrollable elements up too and I end with a black modal content. Now I have a site where I have to put in very long texts with many images from an images field below the CKE field. That means scolling and scrolling and navigation is very distracting. The maximize button in CKE does not really help. I just finished a couple of Wordpress pages and in that respect it was much easier to handle. Choose maximize and use the full screen, not a scrollable box in a scrollable box in a scrollable box. What do you think?
-
Yes, confusing and not how things should be, I agree. What I did (somewhere in that workflow the trouble started): 1. installing with ModuleManager, as usual -> did not work. Showed no error but acted as if I never had tried and still offered the "download" link (instead of "install" or "edit"). 2. Read in the forum that a manual installation was needed. -> that did not work because the previous attempt left something in the database. 3. Deleted that info from the database -> now the manual installation worked successfully. -> The module works fine now and I am very happy about it.
-
Found it. This did the trick: 1. To start over, I deleted the HanaCodeHelper entry from the database directly (at "modules") 2. Then I found the module after refreshing Modules in the Admin under the "install" tab and could install it normally (Is it because the Helper code has no uninstall code yet?)
-
Hi teppo, good news that it is working at your install. So there is hope Your questions: I do not see js errors (only the [Error] TypeError: null is not an object (evaluating 'e.length') which comes from the very outdated jQuery, the PW core still uses.) i am on MAC Yosemite with Safari, Admin Theme is Default, PW ist latest DEV. I do NOT see the mentioned line of code in the template source. UPDATE: I was tricked by the ModuleManager. The Plugin was downloaded but actually never installed. Since there was no warning, I thought it installed. So I have the sort of installation problem reported here before - and not a display problem, what I thought. I am on PHP 5.6. / The Helper code does not use PDO database code yet. ...maybe that plays a role?
-
Yes that's what I was meaning: contextual menu is broken here (latest PW dev). I see "paste" but nothing else.
-
I tried Hanna Code today for the first time and I am amazed how cool it is. I also tried the Helper. It installed without issues. But I can't see the new Icon appearing in CKE's contextual menu. Maybe this has to do with the many changes CKE at Processwire had since the release of this Helper module. Is there something I need to set in the CKE field settings? Like adding Plugin info manually?
-
On one site (using the dev version of PW, I misconfigured the field settings somehow to close and return to the field-list after each save every time. My settings in the AfterSaveAction module are ignored in that case. I just cannot remember where that setting was, to revert it to the normal behavior. A global PW setting somewhere? A module? I really have no idea. Has anyone a hint for me?
-
MarkupSEO - The all-in-one SEO solution for ProcessWire.
ceberlin replied to Nico Knoll's topic in Modules/Plugins
Hi Nico, >Canonical >Yes it's $page->httpUrl I see a potential double content problem here: A page can exist in http and in https mode. Especially after a https page was called (admin area, or a form in the frontend for example) a user stays in https mode until a next page which is set as http-only was opened. Do you agree that a double content issue is possible? If so, my idea would be using this checking order: 1. is the whole site https only (the brand new setting option in the latest dev) ->https 2. fallback: is there a strict setting in the URL part of the template for https? ->https 3. fallback: use the common way to display a website ->http What Do you think? -
MarkupSEO - The all-in-one SEO solution for ProcessWire.
ceberlin replied to Nico Knoll's topic in Modules/Plugins
Hi Nico, it's about time for me trying your module. Fist of all: Thank you for sharing! I have a question about the title (or maybe a wish): The title can be pre-filled automatically. I like that. But it is limiting for me. Right now I have a separate field for the window title, called title_window. The reason: This gives me the freedom to name the page differently in the admin (for the page list and selections) and the real title output. The title is filled in by the editor and the title_window is left to set by the seo guy. In case the title_window (SEO) is not set, there is a fallback to the title, when I output the site. (I think that is the way Wordpress handles that too, in combination with the SEO module, if I recall this correctly.) (EDIT: Why an extra field and not the module: I do not like the tab clicking to the SEO area in the normal workflow of an editor. I want the editor to have the title and the SEO title close together. - But this is a matter of taste) Is there a way to mimic that in the module? Select a custom field with a fallback to title? (Of course there are workarounds for me - maybe this idea finds friends in the community But maybe this makes things too complicated. ) And some small thoughts: canonical I would like a comment to the canonical tag field what default you set in case the field is empty. (it is probably the page url without segments and variables?) segments and variable A question is how to handle segments and variables (page numbers) best? I use segments and page numbers for filtering content. To avoid double content I set my templates manually at the moment to set a noindex tag in case a segment or page number is found. I wonder if this is good practice/needed when there is a canonical tag. link rel="alternate" hreflang On my multi-language sites I have something like this: <link rel="alternate" hreflang="en" href="http://mysite.com/en/press/" /> <link rel="alternate" hreflang="es" href="http://mysite.com/es/prensa/" /> <link rel="alternate" hreflang="en-us" href="http://mysite.com/us/press/" /> This links same content in different languages together for Google. Depending on how languages are set up on the site, the module could easily write such code automatically. (Right now I have some hand coded stuff which does exactly that...) EDITED -
What I did was setting the path as a setting within my user-login template, using a page field (with the output set as single page). So the admin/editor can choose where to redirect frontend users to. Nothing hard coded there.
-
It would be great if I could set the maximum number of backups created by this module I want to keep.
-
Thank you Guenter55 - much appreciated. I personally prefer not to alter pw-core or module code myself (which would be overwritten with any next update) but to report this here so it get fixed for everyone, eventually ...one day ...maybe ;-)
-
MarkupSEO - The all-in-one SEO solution for ProcessWire.
ceberlin replied to Nico Knoll's topic in Modules/Plugins
I deleted the module directly from the database and installed it again. Yes: install/uninstall is fine when doing a fresh, clean install. The update was the problem. -
MarkupSEO - The all-in-one SEO solution for ProcessWire.
ceberlin replied to Nico Knoll's topic in Modules/Plugins
Hi Nico, I tried your module today, installed version 030 first from a previous download, then upgraded to the current version 060. After that I tried to uninstall the module to try that out and got an error: Catchable fatal error: Argument 1 passed to Fields::___delete() must implement interface Saveable, null given in /mypath/wire/core/Fields.php on line 265 -
On installations and updates appears the well known warning whether to trust the source of a zip flle. A useful reminder. But there is only a "yes/no" modal. You do not see that link displayed anywhere (or only encoded in the browser's status bar, it that bar is set to "visible"). - I am always temped to click "yes" and simply ignore the warning. I was thinking whether some more evaluation before a download would be useful to add some security: maybe at least showing that link in the modal dialog. maybe having an active link to the corresponding GitHub/Bitbucket page - so you can open if and, on updates, quickly look through the changes there first maybe give a louder warning if the target is not a zip file coming from GitHub/Bitbucket.
-
Hi Netcaver, I double checked with my MYSQL software NAVICAT. I can confirm now that the problem of false errors is there. I found what those affected fields have in common: The module reports totally wrong MysQL overhead warnings of abt. 300 MB (always the same value for any of the fields in question by the way) for any field that has InnoDB set as engine (instead of MyISAM). This is even for freshly installed fields. In those cases also the "optimize" link has no effect. And for those other fields: a "WARNING" is very dramatic info if shown even for fields hat have something like 32 bytes overhead. Maybe there should be a threshold before a warning is fired. So WARNINGS are not used to excessively with the effect that that real important warnings are taken more seriously within the module. Do you agree?
-
Hi netcarver, I start to getting errors with the module. I think this is because I use the latest PW (2.5.8) dev and something changed. Can't save page 1234: /processwire/access/users/test01/: Call $page->setOutputFormatting(false) before getting/setting values that will be modified and saved. [sla_fail_lastsent]
-
Integrating a member / visitor login form
ceberlin replied to thetuningspoon's topic in General Support
Thanks Macrura. That would work and that is how I had it. Problem is that this would break my security concept the minute I change a role or add one - and forget to update this code afterwards. gebeer, this is so brilliant! - exactly what I was looking for. And you come up with ideas like this at 3 in the morning?